Youโve officially made it! Weโre almost ready to wrap up our conversation about the Scaled Agile Framework. In case your memory is hazy, Iโm a senior consultant and team lead on the Keyhole Software team. Iโve been working with a client who is adopting SAFe, guiding their team and helping to set the right culture for the methodology. Iโve learned a lot about SAFe over the past year, and in this blog series, Iโm sharing what Iโve learned with you.
In this final series installment, weโre getting a bit more practical. Weโll start with a quick foray into the benefits and the drawbacks of implementing SAFe (weโre all about balance here). Then, Iโll talk a little more about what it looks like for small teams, and after, Iโll share some tips for devs who find themselves in an organization that uses SAFe. To wrap up, weโll get down to it; should you implement SAFe on your team? Iโll talk you through a few factors that should help you decide.
Before we get started – if youโre new here, head to Part I (Overview + Core Values) and/or Part II (Core Principles) before proceeding. If youโre caught up, great! I think weโre ready to dive in.