agile.brazism

Posts tagged with "feedback"

What killed us was “one more thing.” We could have easily done three major releases that year if we had drawn a line in the sand, said “finished,” and shipped the darn thing. The problem is that the longer it’s been since your last release the more pressure and anticipation there is, so you’re more likely to try to slip in just one more thing or a fix that will make a feature really shine. For some projects, this literally goes on forever.

-

1.0 Is the Loneliest Number — Matt Mullenweg

Good article about the need to actually ship - “Great artists ship” - that’s summed up in one sentence:

But if you’re not embarrassed when you ship your first version you waited too long.

Getting your product out the door, in front of users, is still the best way to find out what they actually want and need, instead of studies and surveys and interviews. Get people to use it, get them to complain about it, and that single act will provide you with all the information you need to prioritize the “What’s Next” list of features for 1.1, 2.0, 3.0 and beyond.

Ship it. Get it out the door.

Posted on Wednesday 10 November and comments.
ship1.0feedback
The problem with chasing the dream too long is that you end up without the resources to change direction when a PFA comes true. The MVP is intended to counter this tendency. The process of working backward from the assumption to the least possible investment to validate the assumption saves resources in the case of difficulties and keeps the business on the path of learning.

-

Three Rivers Institute  » Blog Archive  » Approaching a Minimum Viable Product (emphasis mine)

Isn’t learning one of the core benefits of Agile development? Closer contacts with customers, to learn what they want, how they work. Shorter release cycles to get more frequent, validating feedback, to learn whether your product is on the right track.

Watching our team struggle with that validation, seeing a backlog of items sit unreleased so that the product can be released “as a whole collection of features” is really hard. Our Agile team has hit a waterfall product release schedule, and it affects morale on the team so quickly.

It’s frustrating, but changing the traditional “a product is this collection of features, and the next upgrade *has to* add these new features” mindset is proving very, very difficult.

Posted on Friday 7 August and comments.
mvpincrementsreleasesfeedback

About

talkin' the talk, with the battle scars to back it up

Ask me anything

Search

Following

Lynx theme created by Andrew Stichbury for Tumblr.