Impediments can slow down your Scrum team, or on a larger scale, block your organization’s Agile adoption. Here are four practical steps you can use to remove impediments and stay on track.
Release planning requires more than dates on a calendar. You need a strong Product Backlog as well as a shared Product Vision. In this how-to guide we provide a comprehensive review of the process and helpful frameworks to get the job done.
Are your Sprints getting bogged down or missing the mark? Scrum with Kanban might be the answer. We provide a comprehensive explanation of how Kanban can improve your process with Task Boards, Team Boards, and a better focus on customer needs.
Regular, well-run retrospectives are critical to the ongoing improvement of an Agile team. In theory, scaling this process into an enterprise-wide activity sounds like a great idea. The reality of large scale retrospectives is quite different, however.
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.
Many Development Teams do not have the communication “muscles” to effectively speak to Stakeholders directly during Sprint Demos. We provide suggestions and a framework to strengthen the Development Team’s ability to make their Sprint Demos awesome.
The software architect has a vital role on the Scrum team. Find out what the architect’s four key areas of responsibility are, and get some top-notch recommendations for further reading.
Sprint Reviews can be dull affairs with little useful output. Instead of focusing solely on the demo, we recommend creating an environment focused on collaboration — and saving some time for celebration.
Remote Program Increment (PI) planning poses unique challenges to SAFe teams accustomed to working together in person. We propose solutions to get your team prepared.