1 / 9

Client requirements as key for project success

Client requirements as key for project success . Rabie Adel 122938 YVEMM. Content. -Introduction -Strategy How to gather the customer requirements and Questions to be asked to define the requirements

morrie
Télécharger la présentation

Client requirements as key for project success

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Client requirements as key for project success Rabie Adel 122938 YVEMM

  2. Content -Introduction -Strategy How to gather the customer requirementsand Questions to be asked to define the requirements -Conclusion - References

  3. Introduction What makes IT project successful? Meets Client requirements

  4. the ultimate goal of all parties in a project is to satisfy fully the requirements of the client. Client requirements constitute the primary source of information for a construction project and therefore, are of vital importance to the successful planning and implementation of a project.

  5. Strategy • Understanding the customers' needs • Identifying requirements • Clarifying and restating requirements • Analyzing requirements • Defining requirements • Prioritizing requirements • Allocating requirements to the components of the system • Tracking and managing requirements • Testing and verifying requirements • Validating requirements

  6. Types of Requirements • Operational distribution • Functional- what system must do • Data - structure of system or data necessary • Usability - acceptable levels of user performance & satisfaction

  7. Techniques • 1. one to one meeting can promote more detailed discussions • 2.Group Interview meetings speed the process of gathering requirements. 3. Facilitated sessions allow for much larger groups to further speed the process and may allow you to gather all requirements in one session and move the group toward consensus 4. Questionnaire

  8. Conclusion • Gathering accurate business requirements is a critical step to the overall success of your project. All projects have some specific business outcome they are attempting to achieve The client may not have had a clear idea of exactly what was required and may have asked for something they thought they needed. Or the supplier may not have accurately determined or analysed the client's needs • We need to gather requirements and document it in details of what the client has asked for it, to serve also as a reference document for testing the system in the future, we have to confirm the client happy with the analysis of requirements if got the accurate picture of these requirements which will be as the first and main step of project success.

  9. References • 1. http://www.projectmanage.com/project-management-and-customer-requirements/ Project Management and Customer Requirements • 2. CAPTURING CLIENT NEEDS IN REFURBISHMENT PROJECTS http://www.arcom.ac.uk/-docs/proceedings/ar2005-0865-0874_Lee_and_Egbu.pdf 3. Book name : Introduction Systems Engineering Fundamentals Link: http://www.dau.mil/pubscats/PubsCats/SEFGuide%2001-01.pdf chapter 4; 35 -45 http://www.klr.com/articles/Articles_BA_GatheringBusinessRequirements.pdf 4. Article title: Gathering business requirements

More Related