Too many organizations confuse doing agile with being agile. They force adoption through command-and-control thinking combined with predictive planning. That won’t work. In this series of excerpts from their new book, Craig Larman and Bas Vodde share best practices for adopting and scaling lean and agile development.
32 items found
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.
The approach to scope changes used within the agile/Scrum framework provides a stable environment so the development team can focus on getting work “done.” Frequent feedback about the product allows for less upfront planning and means the Scrum team can quickly adapt to changes. Delivering business value early and often results in increased customer satisfaction.
Anxiety and strain on the job is normal, but in the process of using Scrum it is common to find product development groups and senior management going head to head. Here we look at some keys to its successful implementation.
Scrum Alliance’s 2015 version of the State of Scrum has just been published. It contains some very interesting insights that we should all be aware of.
A well-functioning Scrum project requires three distinct roles, separate but equal: the Product Owner oversees what is being delivered on behalf of the customer; the Scrum team controls how they work; and the Scrum Master facilitates and acts as keeper of the process on behalf of the organization.
The new Added Qualifications certificate-based program will provide training in more advanced, business-critical topics, starting with Scaling Scrum Fundamentals.
Even in a tough economic climate, small-business owners and executives can build stronger companies through commitment to the tenets of Scrum, which include creating a culture of learning, embracing prioritization at the organizational and team levels, and seeking out feedback loops.
Is the product owner the most stressful position in Scrum? It can be a thankless task, and here we explore their responsibilities (thankfully, it isn’t all bad news).
Some substantive updates to the definition of Scrum artifacts may seem like minor clarifications to terms and definitions, but they have quite profound implications. In this article, we discuss these changes and how they affect the ScrumMaster (or project manager) tasked with delivering a “done” increment.