Lean-Agile
Coaching and Training
Other
-
- Also some Useful Tools
Note that we have some Incomplete Pages That Require Work on this site:-)
Note that we have some Incomplete Pages That Require Work on this site:-)
Or “Its in the Feature Acceptance Criteria!”
Epics and Features become the new way to specify fixed scope that is required to be completed before it is considered “done”.
Many traditional organizations, has controlled work by specifying in detail plans of work. This is both:
Agile assumes that in many cases you cannot know everything up front and so it puts in place feedback loops so you can learn as you do the work. If you do not take advantage of these feedback loops you really are just wrapping a fixed scope mindset in an agile wrapper.
A fixed scope mindset results in a number of issues for an organization but they can be summarized as follows:
The result that your organization will be the opposite of “a learning organization optimized to deliver highest priority business value fastest.” Given this is often one of the main agile transformation, this does not bode well.
At every review point, demo, etc. (in other words, we have feedback loops in place) we should be asking ourselves whether in makes sense to stop working on something, continue working or change our direction - pivot or persevere. There are two questions that can help drive this discussion:
In general there are a lot of ways this surfaces in an organization: