Scary

It’s time for something scary (it’s October 31st after all).

I shuttered as I read this part of the Agile manifesto:

“Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.”

Terrifying, right?

That’s like saying “Rewrite the speech the night before the conference” when you learn your topic doesn’t fit the theme.

Or you need to enlarge all the doorways in a house just when the drywall was hung because you found out it needs to be handicap accessible.

Often it feels too scary. Too big of a delay. Too much stress.

We'd rather deliver the wrong thing, on schedule, as planned than welcome changing requirements.

Only when you are committed to outcomes and not activities or deliverables can you do this.

If you are scared or resistant to changing requirements, pause and ask yourself why.

If you ever need help welcoming

changing requirements

for your data team

I’m here,

Sawyer