Had a chat with two long-time agile practicioners the other night, and the
disappointment of Scrum not keeping is promises is real. But I think it's caused
by teams blindly copying and focusing on processes to enable more (!) WIP, and
not outcomes.
2 replies
Replying to @coderbyheart
Delivering value to the customer is the single most important responsibility of
a team, all process should be a support function that maximizes that. If teams
do not measure that but are happy with counting story points, # of closed
issues, they are optimizing for busy work.
Replying to @coderbyheart
Scrum is good for executing defined work items, but it's an embedded process in
a larger system and the most impact happens earlier: the decision which story is
going to be realized. Prioritizing stories is hard and doing it properly takes
time (and vision), too few see that.