Posts Tagged ‘project scope management’

Launch of Scouts Canada’s Revitalized Uniform: A Case Study of Excellent Project Scope and Communications Management

27 March 2011

Scouts Canada: Project Scope and Communications ManagementSeveral things went right on the recent launch of Scouts Canada’s revitalized uniform but there are two project management knowledge areas that the team focused on that made it really successful—project scope management, particularly the Collect Requirements process, and project communications management.

To respect the movement’s century-old history and to address potential emotional concerns, the team spent countless hours gathering the requirements via formal studies, surveys, focus groups and face-to-face discussions. Without a well-integrated project communications management plan, the requirements gathering process would not have been successful.

Throughout the project, updates were sent to more than 100,000 members whilst continually engaging the senior management team, and local staff and volunteers. The resulting media coverage in national newspapers, radio and television—and the buzz on social media sites—points to a solid and well-executed marketing and public relations strategy.

Connect with Dr. John A. Estrella via Facebook, LinkedIn and Twitter.

Traceability Matrix: Letter vs. Spirit of the Law

26 March 2010

Project Management Audit - Traceability MatrixAfter posting my blog about project scope creep, Joshua Milane asked if I am a proponent of traceability matrices. I replied YES.

He immediately sent me his preferred approach. It is a good article particularly for practitioners who occasionally prefer the spirit vs. the letter of various methodologies, processes and standards.

As long as the job gets done, is it really necessary to have physical vs. conceptual traceability matrices? In my projects, I have never seen the former per se but I know that we can:

- trace the origins of requirements
- map the design against the requirements
- vet the solution against the design
- pinpoint where a change came from
- identify who signed off on the changes

We use unique IDs for requirements, test cases, defects and change requests to link various artefacts. Do we need more?