Our client Visma Commerce has decided to go SAFe with us as a strategic partner.
The Scaled Agile Framework implementation strategy includes the following;
1. Training of the entire R&D in Leading SAFe – Even SCRUM Teams are trained in this to get the overall understanding and appreciation of lean production flows and calibrated concurrent backlogs for Teams, Programs & Portfolio initiatives in the enterprise and “see the big picture”.
2. Tool customization to accommodate SAFe – Jira & Jira Agile is primarily used combined with our “developed” gadget for SAFe reporting. In addition introduction and support for COD & WSJF weightings and calculations on Program & Portfolio levels has been implemented.
3. Adoption of SAFe – A somewhat mid to long term strategy – Here the journey begins by adopting the the time fixed PI Cadence, Joint Release planning, Continuous Delivery and Test Automation concepts
To date we have trained 60+ people in Leading SAFe concepts and the feedback has been overwhelming. Some voices from the trenches
- “The SAFe training was very inspiring”
- “The SAFe training was almost like a team building”
- “The SAFe training demonstrated the purpose & big picture of the company’s future”
Some of the teams immediate reactions as part of their retrospective was to embrace for instance
- WIP limits on various levels in the SAFe model and various columns to prevent “Overflow”
- Set a more rigid priority on Stories & Tasks
- Have common planning sessions and retros in a common facility at the same time
- Using Story Points and relative estimation instead of hours
- Load Balance 70/30 of MUST/SHOULD’s for an iteration and a PI
- Invest more in Continuous Integration/Delivery
- Ownership on User Stories
- Adoption of WJSF & COD concepts to shape Program backlogs
- Adopt common Release planning & I&A ala SAFe
- Invest more effort of defining good acceptance criteria on both Features and Stories