Download
managing projects in organizations n.
Skip this Video
Loading SlideShow in 5 Seconds..
MANAGING PROJECTS IN ORGANIZATIONS PowerPoint Presentation
Download Presentation
MANAGING PROJECTS IN ORGANIZATIONS

MANAGING PROJECTS IN ORGANIZATIONS

134 Vues Download Presentation
Télécharger la présentation

MANAGING PROJECTS IN ORGANIZATIONS

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. MANAGING PROJECTS IN ORGANIZATIONS J.D. FRAME

  2. Making Certain the Project Is Based on a Clear Need • Chapter 4 • Reviewed by Regina Smith

  3. Identifying and resolving problems associated with formulating customer needs.

  4. The Needs/Requirements Life Cycle • Needs Emergence Phase • Needs Recognition Phase • Needs Articulation Phase • Functional Requirements • Technical Requirements

  5. Needs Emergence Phase • Internal Needs • Improving organizational performance • business reengineering • External Needs • environmentally generated needs • more powerful computers • better tasting food

  6. Needs Recognition Phase • recognize the need for what it is • make a conscious effort • establish procedures to do it systematically • focus on existing and future needs • forecasting • scenario building • Anticipate future emergence of needs

  7. Needs Articulation Phase • An in-depth scrutiny of the recognized need. • Looking below the surface • Stipulate in concrete terms what is needed to achieve it.

  8. Five steps to articulate the need • Ask customer to define the need as clearly as possible. • Ask a full set of questions about the need. • Conduct a complete research effort to enable you to better understand the need. • After the first three steps, formulate the need as best you can. • Ask the customers to respond to your formulation, then revise it as needed.

  9. Functional Requirements • Describing the characteristics of what you plan to deliver. • Described in ordinary language for the lay person. • Use graphic images to strengthen it.

  10. Technical Requirements • emerge from the functional requirements • written for the technical person.

  11. Pitfalls in Defining Needs • Problems with inherently fuzzy needs • Problems with identifying solutions before the needs have been fully defined. • Problems with addressing the needs of the wrong customer.

  12. Pitfall one - Dealing with inherently Fuzzy Needs • Two characteristics. • Needs are dynamic • needs are rarely understood by the customer.

  13. Dynamic Needs • Changing players. • Changing budgets. • Changing technology. • Resolution • Avoid casting needs in concrete. • Be aware of the changing nature of needs.

  14. Misunderstood Needs • Customer may not fully understand the need and the implications • Project Staff must: • recognize guide the customer • help customer identify their need clearly.

  15. Pitfall Two - Identifying Solutions Prematurely • Short cutting the needs articulation process • Articulation process is an evolutionary process. • Leave options open

  16. Pitfall Three - Addressing the Needs of the Wrong Customers • Sort out the needs of multiple customers • Establish priorities by creating a needs hierarchy using a small cross -functional team of staff. • Distorting the Customers Needs.

  17. Distorting the Customers Needs • Gold - Plating of needs. • Selective filtering of customers needs by injecting your own personal bias. • Practicing the father-knows-best approach to needs recognition and articulation