Attention: This article was published over 2 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.If you work with Java, you’re likely aware that performance is crucial. No one wants a slow application, especially when scalability and user experience …
Attention: This article was published over 2 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.Have you ever wondered why some companies remain committed to Java while others thrive with .NET? As technology rapidly evolves, making the right choice …
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.
Attention: This article was published over 2 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.Has your Python application been running a bit slow lately? We’ve all been there! Luckily, continuous profiling can help you catch those sneaky performance …
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.