Phase
1. Understand the problem and its context
Need to understand problem
as fully as possible -- in the context in which it occurs.
Remember: many projects fail because the process didn't include
thorough analysis of the problem. Don't skip it!
Steps:
1) specify objectives.
Tools:
- "hopes and fears" -- each member of group says what s/he hopes will happen -- or fears.
- visioning
- service objective
- strategic framework
2) identify and assess influence of all stakeholders
do stakeholder analysis exercise.
- positioning chart --places stakeholders on 2-D grid showing degree to which they support or oppose the project and their importance to its success.
3) analyze need or problem in detail.
"Often the problem or objective is embedded in at least one work process. Process analysis is therefore a good way to delve into the details, understand the bottlenecks, see the handoffs, and identify where information is added or recorded. A process map that shows this in sufficient detail is then ready for preliminary process improvement ideas where the work team identifies ways to streamline or get more value from it."Non-process problems need other tools:
- Self-assessment tools gather information about current situation.
- Models of the problems can help to make your situation more explicit.
- Interviews or surveys
- Statistical data
Result should be "a clear, unambiguous, shared understanding of the business or program objective you want to achieve. " Problem is that project directors often don't do this step: assume everyone sees situation in same way -- not the case.