Scrum has been at the forefront of a revolution in how software is developed and deployed. Who is using it? How? And why? In this exclusive 48-page report from ProjectsAtWork, Scrum Alliance and ProjectManagement.com, 500 professionals share their answers.
Just as agile teams strive to continuously improve, they should also continuously seek opportunities to reduce wasteful activities. A good start is creating visual representations of a team’s total wasted time over the course of several sprints as well as its time invested in improvements.
Are your project retrospectives getting a bit stale, diluting their effectiveness? Keeping retrospectives fresh for your team requires diligence on your part, but the rewards from continuous improvement are worth it. Here are three fun, simple retrospective techniques that can help get your teams re-engaged.
Scenarios and storyboards are great tools to describe how users interact with a product. They also complement user stories by helping to explore risk, discover new user stories, and capture the relationship between stories. Here is a primer on what these tools are, and how they can be used in an agile context.
How can your team accurately predict and communicate meaningful delivery timelines when it is constantly fielding changes from the multiple business units it serves? Here is a detailed look at how one Scrum-centered team used a four-step approach to estimate timelines for work far into the future.
Stephen Denning, author of “The Leader’s Guide to Radical Management” and thought leader on innovation and organizational storytelling, recently joined the Scrum Alliance board of directors. Here, he discusses what drew him to Agile thinking and his efforts to bring the spirit of Scrum to new environments and to make it more resilient, scalable and sustainable. [15:15]
In the quest for continuous team improvement, identifying corrective actions through retrospectives is only the first step. Those actions need to be agreed upon by the team, made visible and tracked by the Scrum Master, revisited at the next retrospective, and celebrated upon successful implementation.
Scrum Masters use different props and materials to plan, estimate, conduct retrospectives and maintain information radiators such as task boards. This collection of “stuff” is key to creating a visible, tactile work environment that engages team members. Here is a detailed look at the contents of one such “Agile Kit.”
The iPad and agile project management seem to be made for each other with their shared emphasis on simplicity. And as enterprise mobility grows, iPad apps can and will be used to manage product backlogs, release lists and sprints. Here’s a look at three agile PM apps available for the iPad.
ESI’s Matt Ferguson talks about realistically assessing an organization’s agile needs and readiness, focusing on three key variables: knowledge, application and support. He also sees the emergence of a “three-party system” in project management, representing traditional, agile and hybrid approaches. [15:30]