Second getting them to understand Story
Points, a seemingly meaningless measurement, seemed to be a non-starter
for them.
Switch - Heath Brothers Heath Brothers - 0 views
Agile Project Management Blog - 0 views
-
-
deal hours first This is where ideal hours came to the rescue. They were far more able to wrap their heads around ideal hours i.e. if you lock the developers and testers in a room with zero interruptions, how long would it take. I figured that once they got their initial stories estimated in ideal hours down, switching to Story points will be easy as they would have established a scale of reference to compare against. This approach worked really well. They're now into their 3rd Sprint and now that they have an existing scale, whether the number is in ideal hours or story points or dog points for that matter, it really doesn't matter any more. If you're new to agile estimating, and you're having trouble coming to terms with Story Points try this first and then make the switch later.
James Shore: Value Velocity: A Better Productivity Metric? - 0 views
-
*Please note that I'm specifically talking about productivity. Velocity is a great tool for estimating and planning and I'm not trying to change that. It's just not a good measure of productivity.
-
rather than asking your business experts to measure business value after delivery (difficult!), have them estimate it beforehand. Every story (or feature--keep reading) gets an estimate before it's scheduled. At the end of each iteration, add up the value estimates for the stories you completed in that iteration. This is your "value velocity."
-
And rather than reflecting the hours programmers work, as cost velocity does, value velocity actually reflects productivity. Remember, productivity equals output/time. Value estimates are a much better indication of output than cost estimates are.
- ...7 more annotations...
Tailor your Message To Gain Support for your Agile Initiative | Enabling Agility - 0 views
-
Connect Agile’s Benefits to your Company’s Priorities
-
aying that Agile is “better, faster, cheaper” may not be enough to cause a company to be willing to go through the often-painful process of cultural and process change. You could implement Agile, but you could also try Six Sigma or Lean. Saying that Agile is a general get-better remedy puts it in line with many other get-better methods.
-
f they don’t see a meaningful update from us, at least once a quarter, we’re going to get kicked out of the game. We’ve all acknowledged that as we’ve gotten bigger, our processes have become more cumbersome and now is the time to do something about it. Agile will give us the ability to regain that rapid pace of delivering innovations to market that we were know for in our early days.”
- ...21 more annotations...
1 - 5 of 5
Showing 20▼ items per page