Adventures in slicing features.
Teams need to learn the artful skill of slicing features into stories a related to their business context and domain purpose. A typical anti-pattern is for teams to waterfall their iterations, as described in the next two scenarios.
The first iteration we will gather all the requirements, the second iteration we will design, the third and fourth iterations we will build, and the fifth iteration we will test…and so on…
Another derivation of this anti-pattern is to order up another form of phony business agility and/or Scrum.
In this iteration we will pull “requirements gathering” stories first. When those are all finished, we will pull the “design stories”, and then “build” stories…
The next common anti-pattern related to intra-waterfall is for dev team members to pull stories and work on them independently. This is a siloing ant-pattern, indicating the team is not cross-functional and is simply a collection of silos and individual waterfalls. Read the rest of this entry »
The fourth tool created to date by blogagility.com for the community!
This handy starter kit is for Scrum masters that are using the Shu Ha Ri paradigm for team development. Good coaches help new teams avoid the pitfalls of added complexity involved in “Agile Lifecycle Management Tools” and instead push for good old-fashioned manual BVIR’s, Kanbans, Scrum boards, et cetera. Change is hard enough in a CAS without adding to the problem by also complicating the way of working. Read the rest of this entry »
Artificial Limitations are not controls
Don’t limit your team to using just Scrum or Kanban. Don’t even limit yourself to using watered down versions of a combination of Scrum and Kanban. High-performance teams master both the empirical process framework and controls called Scrum, and the use of Kanban (system; Lean).
Continuous Learning (The Three Ways) & Empiricism
Continuous learning teams know how to scale these frameworks and systems using the SAFe and other scaling frameworks to suit the needs of the business and customer solution context (value). Learning teams know how to drive DEVOPS culture and practices through self-organization and self-management.
Scrumming it, the next step
If you are practicing Scrum, and using a Kanban to support the process framework it is helpful to walk the board during the Daily Stand-up (Scrum). Do this a few times a week rather than asking the three questions every day.
#Scrum #Kanban #Agile #Lean #SAFe #scalingframeworks
SAFe® The Evidence Series #1
Check out the amazing things that high performance, motivated teams can do. This is business agility and Lean-Agile culture at its best. The transformation of my client’s organization is amazing. We are using Lean, Agile, Scrum, Kanban (and systems thinking), SAFe®, OrgMindset®, and other tools to inspire and persuade a positive change in culture at the FAA-ESC.
It is hard work, but it is worth every minute of it. It isn’t perfect, but the results are significant and measurable. The “why” was a burning platform. Now, just a few PI’s later, it is a thriving platform. We focus on the goals, not the tools to achieve positive business outcomes.
Congratulations to Team Armada for winning the “Relentless Improvers” innovation football for PI6.
Big kudos to John Wiese and his team for putting together an awe-inspiring PI System Demo.
Special thanks to the FAA-ESC, John Wiese, and teams for providing permission to publish the video under the safe harbor notice/policy. Also, special thanks to Matt Taylor for sharing a different video perspective as a content contributor.
#SAFe #Agile #Culture #OrgMindset #BigLakeSoftware
The newest VersionOne 12th Annual State of Agile Report was released on April 9, 2018. Last year I compared the growth of scaling frameworks and methods to each other year over year. (click here to see the report from last year) Read the rest of this entry »
A short story, April 11, 2018, by Marshall Guillory
It was that day again. Powerpoint Commando day. Just like every day on this job. I had never felt more frustrated in my entire career. After all, why did I spend so much of my life educating myself and gaining all of this great business experience and honing my skills if I was going to be reduced to the modus of a PowerPoint clown? That’s what it felt like at least when my VP, a charismatic and gutsy leader, Mike, would call and ask, “Hey do you have those quad charts for the Falcon program updated for the executive review tomorrow?” Read the rest of this entry »
Did you know that the value of facilitating retrospectives is also valuable at scale? In other words, facilitating cross-organizational retrospectives. Improvement is necessary to create better business outcomes. Relentless improvement should be a prime directive in every Lean-Agile organization.
In particular, if you are working within a Lean-Agile SAFe® portfolio you may be familiar with some of the following retrospectives. Others may not be so obvious. The point of which is that we should retro our performance for significant activities/ceremonies. When there are obvious bottlenecks in the system, do a retro, and use wisdom when this is not the case. And remember the easiest way to fail at a retrospective is to neglect to create improvement stories that make their way into the backlog. Read the rest of this entry »