Estimating anything in the world of software development is hard — these proven Agile estimation techniques make it a lot easier.
Designing the optimal Agile team space got a lot harder when remote work became a requirement. This article suggests a new approach for remote and hybrid teams.
Relative Estimation is the fastest and most reliable method for Sprint planning. Using historical data in the form of Reference Stories makes it even better.
We recently published a piece describing why we think Relative Estimation is a more effective alternative to Planning Poker. In this article, Principal Consultant Joel Bancroft-Connors explains how our recommended alternative, Team Estimation, works.
Estimation is hard. Even the most experienced development teams miss the mark with traditional time-based estimates. The most popular alternative, Planning Poker®, sounds fun, but falls short in practice. In our experience, Relative Estimation is far more effective — and it can be gamified too.
The Scrum Master’s role revolves around service to the organization. This sense of duty includes creating a learning environment that is continuously inspecting and adapting. At Applied Frameworks, we’ve learned that building Communities of Practice is the surest way to embed a learning mindset in your organization.
Agile adoption is serious business. However, most organizations don’t put serious time into training their teams to be successful in this new way of working. In this article, we summarize lessons learned from coaching dozens of organizations through the process.
The framework Six Thinking Hats (6TH) can hone your Agile Leadership planning skills and improve your Agile adoption. Find out how it works and download a complete walkthrough of a retrospective using our Six Thinking Hats Technique Framework.
Selecting the wrong Agile metrics can actually block improvement — or make matters worse. Keep these five principles in mind when choosing metrics for retrospective improvement and forecasting.