PI Planning
Kendis has released a new update focused on Analytics. Before we explain the update in detail, consider this scenario: You’ve your Program Board neatly mapped out: Sprints drawn, Features pulled in, Stories sized, Story Points estimated, Teams assigned. Seems like a good place to be in, right? But despite
PI Planning
In the latest Forrester report about the state of Agile, “unplanned work” is cited as the biggest barrier in fully implementing an Agile approach: To come across such 'asteroids' of unplanned work is not uncommon in Agile transformation. This is a fairly frequent tracking stage hiccup. At the
Scaled Agile
Spotify has cemented itself as one of the best music streaming apps surpassing Apple Music, Amazon Music and Youtube Music. With over 30 teams spread across the globe and having more than 1500 employees, Spotify is thriving. Unlike many organizations that owe part of their success to implementing a well
Scrum
The foundation of having a successful PI Planning session is based on having good coordination and collaboration with all the team members, which could consist of more than a 100 individuals making up the Agile Release Train. The feeling of being united towards a shared vision and being able to
Solution Board
Implementing the Scaled Agile Framework can be an exciting and thrilling experience once the transformation results start to show. But arriving at this stage could take a while. SAFe implementation is interlaced with concepts, processes and a lot of information that can be overwhelming and complex to master without proper
Scaled Agile
User Story mapping is an agile way of planning releases by helping arrange the user stories in a prioritized, clear and perceptible way. It is a top down approach that enhances the visibility and helps in discovering the feature or the product in much more depth thereby clarifying the big
PI Planning
Confidence Vote is an activity done in the Program Increment (PI) Planning session that aims to assess how confident the teams are in delivering progress during the PI. It is done after the objectives of the Program Increment, that need to be achieved during the PI, are addressed along with
PI Planning
There is nothing better than having everyone in the same room for PI planning. But it’s not easy, it’s expensive and not everyone can participate. Kendis offers a solution, which enables teams to plan together from different locations. It will help you manage digital program boards with dependencies,
Scaled Agile
Agile is all about responding to change. That does not necessarily mean that we should leave everything to be done at an ad hoc basis which will eventually lead to a disaster at all developmental and management levels. Thus it is wise to have some level of planning done. A
Scaled Agile
Visibility and transparency are important when it comes to planning or tracking your work items in the Program Increment. All of the work items have stories, dependencies, risks and objectives and failing to correctly recognize or acknowledge them can lead to disrupting a transparent flow of information. To ensure that
Dependency Management
Agile teams are meant to be self managing and independent. But as the size of an organization grows or the scope of the product being developed becomes complex, many teams have to work together. Thus dependencies can start existing between these different agile teams. These dependencies can become a serious
PI Planning
In the Scaled Agile Framework, staying strongly committed to a plan is never advised. The reason is very simple; the requirements of the customer can change. For any professional that is a part of the Scaled Agile Framework, possessing a Lean-Agile Mindset is fundamental. It is in fact one of