In this blog, we’ll explore how CI/CD automation with tools like JIRA Cloud, Jenkins, Slack, GitHub, SVN, and Postman benefits Agile teams as a whole. Whether you’re new to Agile or are working with an experienced team, automation can significantly reduce “JIRA paperwork” while keeping everyone focused on delivering value. By streamlining repetitive tasks, teams can spend more time on …
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.
Welcome back to Part II of our series covering Scaled Agile Framework. As a quick refresher, Iโm a lead consultant at Keyhole Software, and for the past year, Iโve been helping my client adopt SAFe methodologies and practices. Iโve certainly learned a lot, and I want to share that knowledge with you.
Last time in Part I, I gave an overview of SAFe and discussed the four core values: Alignment, Transparency, Respect for People, and Relentless Improvement. Today, weโll dive a little deeper, talking through SAFeโs ten core principles. Next time in the third and final installment, weโll take a practical look at the pros and cons of SAFe and some tips for implementing it.
For several years, I have been a lead software engineer for one of Keyholeโs clients. More recently in the last year, they started a journey to implement SAFe (Scaled Agile Framework) methodologies and practices. If you are new to or have not heard of SAFe, this short, three-part blog series will give you the perfect launch pad.
In Part I (this post), Iโll give a high-level overview and then weโll walk through SAFeโs four core values. In Part II, weโll dive into its ten core principles. In the final installment (Part III), weโll discuss the benefits and drawbacks and then weโll get a bit more practical. Iโll teach you how it can be used for small teams, some key points a developer should know, and some considerations for if SAFe is right for your organization and teams.
Sometimes, Agile isnโt the best choice, even if it is the most highly touted. Sometimes, itโs worth thinking critically about the project and its requirements to select a methodology that works better. In this post, I will explore a few of those Agile alternatives.