From the course: Agile Challenges Weekly Tips

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Projects always have a phase two

Projects always have a phase two

From the course: Agile Challenges Weekly Tips

Start my 1-month free trial

Projects always have a phase two

“

- In traditional project management, teams formed around the work. They were assigned a specific project with a defined scope and deadline. That deadline was the end date, the finish line the team strived for. When they hit the finish line, there was often a phase two to complete the defined scope items that the team couldn't finish. In this context, phase two was another way of saying the project had failed in its mission. It hit the deadline, but left essential scope on the table. Remember, in traditional project management, costs, time, and scope are all locked. There's no wiggle room at all. Hit all three or fail. In Agile work, we don't really do phase two. Let me explain. Agile teams have defined schedule and cost, but no defined scope. It's up to the product owner to define what the most valuable features are for the project to deliver. The PO then organizes the backlog to make those features a reality. If your PO has been prioritizing the highest-value items, and you've been…

Contents