PI Planning
As one of Kendis’ biggest customers, Nordea leads over 150 release trains and has 4,600+ Kendis users. According to Roy Boven, the Senior Process Specialist at Nordea, that number is “still growing, which is nice to see”. Roy and his colleague Adam Guja, a Scrum Master and Agile Coach
Scrum
Scrum of Scrums Feature - the solution you did not know you needed! Greetings from the Kendis team! Here is a quick guide to our new Scrum of Scrums Feature. It will improve the tracking of impediments, dependencies, and accomplishments of your Agile teams, as well as revolutionize the way
Events
With only 3 days before Nordea’s PI Planning, the world shutdown. Join us to hear how the largest financial group in the Nordic countries navigated through the Covid-19 pandemic and used the software Kendis to quickly (and smoothly!) transition to fully remote. You will also learn how Kendis can
Dependency Management
During the Program Increment (PI) Planning, one of the most important activities is being able to understand, discuss and possibly mitigate inter-team dependencies. If not identified, these unknown dependencies would impact delivery of important features anticipated or requested from the business. Thereby, blocking your teams from achieving their goals. During
PI Planning
There have been many discussions about how to conduct Program Increment (PI) or Big Room planning. Initially, it was done in the format of being physically present and would last for 2-3 days in one location. With the arrival of the coronavirus, the concept of Remote PI Planning emerged, where
Scaled Agile
Agile frameworks are regarded as addressing complex problems with the simplest approach to build the most innovative solutions. The iterative and incremental approach really helps in breaking down large chunks of planned work into smaller tasks to create a Minimum Viable Product (MVP) that is enough to ascertain what is
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