In a follow-up to an article on backlog grooming, we answer reader questions about how the process differs from requirements documentation; how prioritization works without a complete picture; how a backlog differs from a work breakdown structure; and how to achieve an “all-in” view of product features when the backlog is a work in progress.
4 items found
How managers change with agile approaches is vital. The more management excellence—the more quality in management—the easier it is to use an agile approach. That requires a change in how managers think about and create the agile culture.
Instead of measuring quality, Agile enterprises commit to it by investing in integration and testing, developing a common language around quality, and nurturing motivated, disciplined teams. Ultimately, quality reigns when organizations value it as much as profitability and protect the agile processes that support it.
How do we define quality as a project manager? Is it managing a project really well, or managing a successful project? How about managing a successful project really well? That sounds pretty good. However, it poses the next question: What is a successful project? Let’s look at some examples of project success, failure and ambiguity.