I wanted to give you a heads-up on an upcoming interview with Dennis McPeak, Technical Architect with RBC Financial Group, since he provides some excellent tips for IT managers. Dennis and his team won the Project Team of the Year Award from Computing Canada announced online in January of this year.
Here’s our discussion on scope creep:
SI: What are your top five recommendations for keeping a lid on scope creep?
DM: For any reader not yet familiar with scope creep – beware! In my estimation, this is the death knell for all large projects. Born out of my experience on this recent project, my recommendations for keeping a lid on scope creep (or change requests) are as follows:
- Capture important information related to the impact on:
- Business Cases
- Functional Designs
- Technical Designs
- Plans and Schedules
- Create a formal process to manage scope creep that includes the following step-wise approach to the change requests:
Look for the interview to appear early next week!
Stephen Ibaraki, I.S.P., firstname.lastname@example.org