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.
It’s weakness to want predictions, to be at mercy of fortune tellers.
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 »
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?
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 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 »
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 »
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... more »
1. .NET folks insisted on TFS with the Visual Studio IDE integration.
2. Jira teams had learned the Greenhopper bolt-on to the bug tracker.
3. Rally users preferred the more natural alignment with Scaled Agile and business-friendly usability.
Software vendors... more »
How long does it take you to get your code out in the market? How can you make sure your Ops team and processes are aligned to support your agile development?
In this session, we... more »
Continuous Delivery involves all dimensions of your R&D and Operations organizations – consisting of Team Collaboration, Agile and DevOps practices, Continuous Integration (CI),... more »