On an agile project, the workload is determined at the beginning of each iteration. The Product Owner evaluates and prioritizes the work that needs to be done, while the team determines the amount of work they can complete. The iteration planning meeting sets the stage and should be run as a collaborative dialogue.
Why do organizations pursuing Agile transformation need a coach and how do they make it stick after the coach leaves? In this new series, we explore these and other questions, starting with Certified Scrum Coach and Trainer Xavier Quesada Allue.
At the release level, we approach the meaning of “done” more strategically by aligning User Stories with Epics and Vision Statements — all of which should be shared across the Scrum Team and all stakeholders so that they can see the building and not just the bricks. Here are some examples of what that looks like.
Managing uncertainty is one of the most important challenges facing project managers, but many have no consistent process for dealing with risks, large or small. One helpful step is to take a page from Agile practices and pay more attention to the size of team tasks and the quality of our conversations about them.
In Part 2 of Dave Prior's interview with Roman Pichler, the conversation turns to the Lean Startup community and how its ideas can add to Agile practices; the value of critical feedback; the willingness to experiment and fail; and the realities of developing Agile teams within larger, traditional organizations. [25:00]
In this podcast, Dave Prior interviews Agile thought-leader and author Roman Pichler about the critical role of product owner in an Agile environment. In shaping and, yes, owning the vision of the product, product owners serve as filter, facilitator and collaborator with project team members and stakeholders. [23:18]
There is a huge difference between using Agile practices and being Agile. Here, a chief engineer discusses his organization’s strides in creating an Agile mindset and a customized approach to producing high-quality work in short time frames. The journey offers practical advice and techniques to those getting started or struggling with Agile transformation.
When planning a sprint, many factors will influence what works best, particularly the experience of the team in self-organizing. Here are some guidelines that can help project leaders focus the planning effort — without taking it over — and a few techniques to engage everyone and establish a shared vision.
Adult children. Jumbo shrimp. Seriously funny. I’m sure you recognize these expressions as oxymorons — self-contradictory phrases, often with an ironic meaning. Should we add “agile requirements” to the list? Does agile development fit in with traditional requirements practices? And if so, how?
Agile practices are not intrinsically “value-adding” — they must be aligned to business needs and goals in order to provide true value. By measuring their agility based on compliance with a particular method, organizations may prevent their teams from adapting practices to suit projects with different characteristics and needs.