SAFe, or Scaled Agile Framework, is a set of principles and practices for Lean-Agile development and software engineering. It provides a framework for coordinating and aligning the efforts of multiple Agile teams, and helps organizations to scale Agile development to meet the needs of large, complex software development projects. SAFe provides a structured approach to…
“A timebox event within Agile Release Train (ART) which delivers incremental value in the form of a working software” is how SAFe defines a Program Increment (PI), and an effective PI requires work to be planned meticulously, transparently, and proactively. This article is an attempt to pen down a few hygiene elements to bear in mind…
In Scrum framework, retrospective is the last event of each sprint and has also been one of the most rushed events in our experience. This has meant that the event has failed in helping the team, consequently failing in its purpose and has thus been considered mostly as an helpless event. There could be broadly…
A “Team” is generally defined as a group of people. Who work together towards a shared goal. In my experience, effective interaction forms the bedrock of such a ‘team’ – a factor often taken for granted. All the more true in an agile environment, where one sees high levels of ambiguity, uncertainty and diversity. Some…
Tracking the progress through typical charts & metrics have often been boring & one of the kind is burn-down chart & hence decided to create my own innovation called the Beer down chart. Imagine, you are in a agile team and have a barrel of beer to finish. Every time you finish your beer, you go to counter and…
Scrum Alliance has published seven versions of Scrum Guide in a decade since the first version was published in 2010. Each version has been a reflection of the changing landscape of software development processes. We have tried to summarize the salient pointers of every Scrum Guide and implications of the changes and updates in this blog. Please…
How do we better utilize our time attending an insane number of meetings? Coaches get this asked a lot. While little can be done about the number of meetings just like driving in bumper to bumper traffic, we can surely improve the in-car time utilization! To make the situation worse, we are in the middle…
Introduction Agile recommends teams to be cross functional and that implies teams to be composed of people with different skill sets who can convert a requirement into a working software. Let’s take an example of a requirement / user story which has come up for a team which involves Design, Backend , Frontend and QA folks. There…
To measure is to know. If you can not measure it, you can not improve it. – Lord Kelvin Like any other assessment, agility maturity assessment also happens at every state of agile implementation & that too frequently. We have used Agile Maturity Assessment in measuring the state of agile implementation at many levels –…
In an Agile project, one most misunderstood concept, which is vital for the project is “Velocity”. While different teams understand velocity in their own way, this blog aims to explain what is “Velocity”? What is the significance of it? And what teams can do to increase it? Let’s try to understand the term “velocity” before…
