If you are a change agent, SAFe® Program Consultant, SAFe® Product Manager, STE, RTE, or practitioner you may find the Blogagility.com™ Feature Progress Chart Template a useful tool for kick-starting your product management (PM) implementation and Lean-Agile reporting. Continue reading “Feature Progress Chart Template”
I read several articles on the subject after having a short discussion during class this week with a fellow student (and amazing person!).
#noestimates does not seem to address the rather common difficulty in achieving a consistent, homogenous backlog with deterministic job durations and delay costs in a CAS. The #noestimates solution fails in the same ways that story points can fail. Yin/Yang. Red vs. Blue. Black & White. Whoopee.
Continue reading “RE: #noestimates sidebar in #SAFe #RTE course.”
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. Continue reading “Paradigm shift: Slicing Features”
#storypoints #noestimates #besmart #orgmindset #scrum #agile #SAFe #LeSS #MOREcommonsenseplease
Or are we still working in the blacksmith shop? Will it take AI to bridge the gap?
In Lean manufacturing companies that build physical things have been able to improve quality consistently and dramatically since the dawn of the industrial age.
Here many of us are in the post-industrial, Information Technology or Digital Age.
When we change the channel to knowledge work, companies struggle mightily to match the pace of quality and outcomes of physical manufacturers, even to this day. Why?
Are these practices, methods, frameworks, and guidance really helping the knowledge worker factory catch up with companies that make physical things? Perhaps there is some evidence to support the claim. Continue reading “The Knowledge Worker Factory”
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. Continue reading “Lean-Agile Team Metrics Starter Kit”
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 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.
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
