Scope Management

Share this:

Hello, Deasún Ó Conchúir from Scatterwork with an anecdote from the book Overview of the PMBOK Guide and this time, it’s to do with brainstorming and scope management. Scope says what is in a project, what work do we need to do? If that’s not very visible, then we can get pushed off track or the scope can change without anyone really noticing and then of course, it’s harder to deliver and then people are disappointed and so on, so management of scope is rather important and in particular, acceptance of the scope.

The anecdote here is that I was consulting on an international project where a new work package was being started. This could have been documented privately and then passed to the project manager for feedback. The disadvantage would have been too little acceptance. When we had the solution, the core project team was at the end of a planning meeting and ten minutes were left before some of the participants had to take taxis to the airport.

Using Post-it notes, forty or fifty ideas of what needed to be done were collected in less than five minutes and after they went away, they were documented. Because the team had participated in the brainstorming, the result was accepted by the core team without question. I think if we had put the same list together and emailed it out, it wouldn’t even have been read. Thank you.

In the modern world, the optimal solution may not be traditional face-to-face training that everybody likes and finds very effective, but virtual training. Please help us to rank our list of virtual training features: Can Virtual Training replace traditional events? (5 minute survey)

Also, if you have any queries, then please select a time to call or send a message.

Invite your colleagues to sign up for the Scatterwork Newsletter and they will also get a 10% reduction on their first workshop.

Share this: