A feature is a collection of requirements that need to be delivered as part of a product. The requirements that form a feature can generally be broken down into stories that form the scenarios which are used by the feature and/or they can simply be the use cases for which a feature can be handled – both are very similar. In short, I like to think of it in this way – it’s a big…
But only if they are great. I love a good half-day meeting. If done right, it means business, it means direction and the measurement is simple. Were these 3 or 4 hours more valuable than a bunch of 1-hour meetings spread throughout the week? When done right, they should be. When done wrong, they will be seen as a waste of time that got you nowhere. The key to a great half-day session is to…
Is it still an error if no one sees it? Of course, it is. But whether it becomes a bug, well that’s up to you, the Developer, to decide how much you care to fix it.
Next is what we are all after. We don’t always know what next is, but we know it is the next thing that we want to go for, it’s the next thing we want to achieve. The goal then is to figure out what you need to do, to get to Next, and start the plan to get there. Sounds like lots of “thinking” work and not enough “doing” work, but if you’re not willing…
When everyone thinks you are delivering something different. It’s a good time, no it’s the best time to sit down with everyone and make sure you are all talking about the same thing. When this happens, you might be the facilitator more than anything in the conversation, not trying to push people to what you see as the delivery, but rather poking holes in what the ideas of others are (respectfully) to make sure everyone…