Ben Woznicki and Tom Cagley provide an even-handed overview (but quick and to the point!) of the concepts behind #noProjects, some history, and the problems #noProject is trying to solve. Thoughts and comments are welcome!
Agile reminds us that the focus of any set of requirements needs to be on an outcome rather than a collection of whats and whos. Storytelling is a powerful tool to elevate even the most diehard requirements analyst from a discussion of individual requirements to a discussion of outcomes. Outcomes are the big picture that acts as an anchor for whole efforts and which is continuously broken down into more and more detailed backlogs. The onion metaphor that is popularly used in agile planning can be used to describe the evolution of backlogs. Building an initial backlog is much like peeling through the layers of an onion to get to the core. There are many mechanisms for developing and maintaining detailed backlogs, including asking, observing, showing, and hybrids. Using the onion metaphor, techniques for developing and splitting user stories are the second layer of the onion. However, before getting to the center of the backlog evolution onion, we need to understand the big picture. Recorded at the Øredev Developer Conference.
Has the adoption of Agile techniques magically erased risk from software projects? Or more frighteningly, by changing the project environment through adopting Agile techniques, might we trick ourselves into thinking that risk has been abolished when it really still exists?
Risk is defined as “any uncertain event that can have an impact on the success of a project.” Risk mitigation, on the other hand, is about predicting the future. Does using Agile change our need to predict the future? I think not. With Agile the difference is our time horizon may be as short as one to two weeks and incorporate both development and testing, so our need to predict risks (and the future) will be different, but does not change overall. What does change is how we approach the topic.
The final punchline is that Agile risk management actually improves project performance. Projects and programs are comparatively faster, cheaper, better and make people feel better but risk has not been erased. Recorded at the Øredev Developer Conference.
Tom Cagley shares a quick tip for being a better agile coach. Never fall in love with a single technique is a reflection on how easy it is to think that if something works once, it will work every time. Tom Cagley is a Transformation Coach & President at Tom Cagley & Associates. Recorded for Vitality Chicago.