Agile scaling is always a hot topic for students and organizations dealing with the complexities of multi-team execution. The question I get asked most often is one that sounds the simplest: “Why does Scaling make everything so hard?”
Both Scrum and Kanban provide principles and practices that you can apply to deliver high-quality solutions faster. They share many similarities but have distinct differences. Both methods were originally developed for software development, however, they can be applied to be more productive in any line of work.
If you’re interested in reducing costs, you may wonder if it’s worth it to invest in Scrum, Kanban, and other Agile training. Here are five ways that embracing Agile can benefit your bottom line.
Interested in doing a sprint review, but unsure what it is and how it works? We’ve answered some common questions about sprint reviews.
If you’ve never experienced what a good Scrum Master does for a team, it’s easy to misunderstand the role as being administrative: scheduling team meetings, taking notes on impediments, nagging people to update the status of things. When that happens, it’s natural for decision makers to feel that the role of Scrum Master is not a real job, and therefore decide not to invest time or money into it. At that point, one of several anti-patterns typically happens. Here are the ones I see most often:
Read about five things to look for to find out what working with a great Agile coach feels like.
In this blog, we’ll explore the purpose of three core reports every Scrum Master should understand and use: burndown, burnup, and throughput. We’ll also explain how to read and create each chart.
The goal of sprint planning is to ensure the Product Owner (PO), Developers, and Scrum Master are aligned on a plan for the upcoming sprint and collaboratively working toward the sprint goal. We’ll cover Scrum Guide’s sprint planning event topics.
Software defects, also referred to as issues, bugs, observations, or oopsies (my personal favorite), are one of your largest sources of wasted time and money. Read more to learn what you can do to fix them fast.
Creating tasks for each user story before implementation may seem like it is adding value and saving you time in the long run, but is it? Is it really? Or is it something you have always done without questioning its value?