The good folks at Scaled Agile, the SAFe® community, Agile agnostics, consultants, and some in the “Agile” community are onto something incredibly important in defining the elusive and dynamic Agile End Game for organizations. Read the rest of this entry »
I am really thrilled to learn more about the Scaled Agile Framework after going through the SPC course and certification process. A big thank you to Eric Willeke as he is an amazing instructor and has clearly mastered the material. I am not a fan of certifications as a KPI for job applicants. Only as indicators of formal education on subject matter. In this case, SAFe brings meaning and harmony to many, many things that we have all been doing for so many years. At least now I have a beautiful framework to show when I talk about organizational transformation, e2 maximization, transparency, alignment, and relentless improvement!
Aside Posted on Updated on
An excellent article by Stefan Wolpers that consolidates his findings of common failure patterns for agile scrum xp, lean/kanban implementations.
reblogged with permission from Mr. Wolpers.
Agile Transformations and ROI
This question was asked recently on a social network Scrum group. I thought that it was very relevant and also a common request from executives that desire an evaluation of ROI for agile transformations. However, it is important to consider both efficiency and the effectiveness of your agile transformation. Read the rest of this entry »
(see also: Agile Moment: Equating Story Points to Time, Scrum Effort Estimation, Practical Guide Story Points Estimation, How Story Points relate to hours, Story Points vs. Task Hours, Planning Poker)
Estimating story points for user stories that implement features on the Scrum teams product roadmap / product backlog is a critical planning exercise. All Scrum teams should utilize planning methods to estimate engineering efforts for future work. There are many possible methods available to estimate effort. However, for teams that are using Agile frameworks like Scrum, a proven, highly effective method of choice is Planning Poker. The overall goal of planning poker is to establish a clear consensus on an estimate for a given scope of work or user story.
Normalization of a relative estimating technique is absolutely critical for a team to reach a high-performance state. This also directly impacts an organization’s ability to perform capacity planning and management in scaled Agile applications.
Jim Whitehurst discussed the interactions or lack thereof between infrastructure and operational folks and the guys who are locked in the closet – developers – in an interview with Fredric Paul (Network World). They discussed the fact that software is becoming ever more omnipresent in technology. It is the first level of interaction for users. People do tend to tune out the sleek new hardware and focus on the software experience. And it better be a good one! Not many end users care about the backend. So, Whitehurst asks the important question… Read the rest of this entry »