Examples are a powerful way to communicate what "done" looks like for agile user stories. When they are automated, they can also act as very useful regression tests/checks. But most automated checks are too detailed to act as useful examples. This can be addressed by using a layered approach to examples in which we provide less detail for broader scope examples and narrower scope for more detailed examples.
Providing concrete BDD-style examples as acceptance criteria for user stories is a powerful way to influence the testability of your architecture. This is especially true if developers are provided the examples before starting development and they are responsible for the automated execution of those examples. This talk illustrate how the examples can have this benefit.
Decide -- Start Small or go all in to transition to Agile -- Learn why each approach has its merits.
Summary It’s weakness to want predictions, to be at mercy of fortune tellers. Outline Anchor’s operate unintentionally and work even when people are forewarned. Estimates anchor and concentrate benefits near the estimate value. In this Pecha Kecha talk I present reasons why the best-benefit outcome is concentrated near the estimated value, irrespective of whether the work gets done sooner or later than estimated value. ...more »
Try Googling that question and you’ll find some strong opinions and clever commentaries. The blogosphere is just filled with opinions on the Scaled Agile Framework (SAFe®), and whether it’s really Agile, or whether it is taking Agile in a bad direction. When building extremely large complex systems involving life critical applications, this becomes much more than an academic argument. When evaluating approaches for ...more »
Provide a day in the life scenario if government organizations were more Agile than Silicon Valley? How would budgets change? How would capabilities be prioritized? What would the culture look like?
The IBM PureApplication team adopted the Spotify agile process in 2014. Since our initial adoption, we have made additional changes based on feedback and best practice. This discussion will talk about the rationale and expectations behind the initial reorganization, the challenges faced through multiple product releases and a large global development team, and the value that was recognized. Finally, a review of the most ...more »
This is a very quick demonstration of an activity that compares metrics between a pizza shop and an organization building software. It is an effective tool for getting to the heart of the agile metrics debate.
Are we getting tired of the kind of "agile" where you don't really have any particular technical practices, change (and improvement) is entirely optional, and you pretty much do waterfall with additional overhead of meetings? Are we tired of seeing "sprints" and "iterations" used as ways to pressure people into working harder and longer ("pushing velocity"), with no training or learning or even autonomy? Are n-week death ...more »
Do you have multiple teams using different methodologies developing one product? Do you find it challenging to support their ways of working while keeping a singular vision? Combining Scrum, Kanban and Gantt is easier than you think. Multiple teams with different ways of working, pulling from the same backlog is a reality. This allows people to work the way they want, while managers always have an up to date view of ...more »
The relationship between Complexity and Simplicity in application development is a delicate balance. There is a rhythm of euphoria and heartache that emerges over the various ups and downs of iterative discovery, development, and delivery. Within a circle of trust and cooperation Complexity and Simplicity dance together in a rhythm that yields application goodness. In this harmony all those involved feel and know that ...more »
In scaling agile, context matters. Being able to customize an agile framework to suit your unique conditions and context is very important. Scaled Agile Framework (SAFe®) is often harshly and incorrectly criticized as too prescriptive or too rigid, and by implications, not easy to customize. Inspired by Dr. Jeff Sutherland’s Scrum at Scale meta-framework which provides a general language for talking about how ...more »