From the course: Program Management for IT Professionals

Unlock the full course today

Join today to access over 24,200 courses taught by industry experts.

Smaller stepping stone projects vs. a big project

Smaller stepping stone projects vs. a big project - Microsoft Project Tutorial

From the course: Program Management for IT Professionals

Start my 1-month free trial Buy for my team

Smaller stepping stone projects vs. a big project

“

- [Instructor] Here we're going to introduce the concept of stepping stone projects. The simple rule of thumb is, whenever possible, break your projects up into smaller projects that are meaningful in the marketplace, that solve some of that customer problem that we defined in the voice of the customer phase. So let's examine why you would do several small projects instead of one really big project. First, bigger projects take longer. They take longer to gel, they take longer to understand, they take bigger teams, they take longer to get to clarity, they take longer to get through reviews, and they are much harder to fund. Smaller projects, in contrast, have all of those advantages, they're easier to fund, quicker to get to approval. Smaller projects also avoid the risk of market and customer change during the project. Shorter projects means the market won't change out from under it. Additionally, smaller projects allow you to apply agile project management tools. This removes…

Contents