Principles Should be Public

I just blogged about Principles Should be Public over at the Pivotal Labs blog.

Once upon a time, there was a client who struggled with the Agile process. It’s not that he wasn’t smart and curious, and it’s not that he didn’t want to build a great product in a domain he knew lots about, but he had a thorny problem: because he was successful, and because he was smart, he just wanted to build this new digital product the way he’d successfully built (non-digital) products before: top-down and waterfall. He didn’t want to make decisions about the details. He refused to look at Pivotal Tracker.

He came to us because he’d heard “Pivotal’s the best”, but he didn’t put together that the process—pairing, testing, short feedback loops, collective ownership of the product, writing the smallest possible stories that deliver user-facing value—were the reason we were successful…

Check it out, and let me know what you think in the comments!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s