It often feels like Continuous Deployment has become a bragging right for a technology organization. “We can deploy 13593 times a day.” “A developer can deploy the product on their first day at work.” “Our pets can deploy to production.” Even more often, I encounter organizations that don’t understand the intent behind being able to …
Picture BuzzCorp (Many of you won’t have to use too much imagination). They’ve invested significant efforts in developing software and products in an agile manner. They formed agile teams (but a deeper look shows those are the existing component/functional teams using agile methods) They manage Features/Stories in JIRA/ADO (but those are the functional slices that …
How do we handle Scope Changes in a SAFe Program Increment? How do you handle a scope change in a program increment? Specifically when it comes to switching one feature for another? And what’s the impact on PI Objectives and Predictability Score? A lot of people somehow get the notion that SAFe advocates for “limiting/controlling …
SAFe™ (The Scaled Agile Framework) uses Story Points throughout the various levels as its estimation currency. This is covered in the “Story” article on the SAFe site. This is a pretty standard practice in organizations scaling agile these days. If you dive a bit deeper into how this is done in SAFe you will see …
When teaching SAFe (The Scaled Agile Framework) we talk about “Ba” — the sense of togetherness and connectedness that amplifies the performance of teams and larger groups (e.g. Agile Release Trains). This week when visiting Leankit (To teach an Implementing SAFe 4.0 SPC4 class to their Customer Success coaching team) I had the opportunity to see their …
Earlier this week I published a guest post about how managers need to change if they want agile to succeed by Yaki Koren. Some blog/twitter followers asked for elaboration and Yaki was gracious enough to comply. I suspect the fact that this is a really hot topic for him this week helped. Without further a …
This is a guest post by Yaki Koren who is the lead coach in one of AgileSparks’s clients – Amdocs Delivery who are going through a very interesting transformation leveraging the Kanban Method, crossing the chasm techniques as well as several key agile practices. It is also where I spend a considerable slice of my …
In the last few weeks I’ve been using a new visualization that people find useful for understanding the relationship between the various Lean/Agile requirement containers. Some people call the full model a dinosaur. Others are reminded of the snake who ate an elephant from “The Little Prince”. (I’m sure there is a good connection to …
The first step is to understand that for a new product to be successful, it should have a unique value proposition. This is the area where your product/service will be exceptional. Initially that is an hypothesis – a bet. The next step is to test the hypothesis as efficiently as possible. We often use Minimum …
Background I recently had a couple of weeks with a few activities related to “Agile Testing”. “Agile Testing” for those not familiar with it is the name we give to the set of thinking guidelines, principles and practices that help run the testing aspects of product development/maintenance in a more effective way under an Agile …