Project Life Cycle and Project Management Process Groupsدورة حياة المشروع ومجموعات عمليات إدارة المشاريع
مقدمة الفصل
ماذا ستتعلم في هذا الفصل
- Understand & describe the project life cycle.
- Describe system development life cycle.
- Describe some SDLC models.
- Describe the project management process groups.
أقسام الفصل
- 1Project phases and the project life cycleمراحل المشروع ودورة حياته
- 2The system development life cycle (SDLC)دورة حياة تطوير الأنظمة (SDLC)
- 3SDLC models: predictive life cycleنماذج SDLC: دورة الحياة التنبؤية
- 4Agile software development and Scrumالتطوير الرشيق (Agile) وإطار Scrum
- 5Project management process groupsمجموعات عمليات إدارة المشاريع
تلميح: استخدم أسهم لوحة المفاتيح للتنقل بين الشرائح.
Project phases and the life cycleمراحل المشروع ودورة حياته
Project phases and the project life cycle
A project is divided into several phases.
The project life cycle defines:
- What work will be performed in each phase?
- What deliverables will be produced and when?
- Who is involved in each phase?
- How management controls and approves work produced in each phase?
Deliverablesالمخرجات
Project phases and the project life cycle
A product or service produced or provided as part of a project.
أمثلة من الشريحة
- Technical report
- Training session
- Piece of hardware
- Segment of software code
سؤال سريع
Project phases and the project life cycle
The system development life cycleدورة حياة تطوير الأنظمة
A framework for describing the phases of developing information systems — product life cycle.
Consists of 4 general phasesأربع مراحل عامة
- 1
Planning
- 2
Analysis
- 3
Design
- 4
Implementation
SDLC: planningمرحلة التخطيط
The system development life cycle (SDLC)
The planning phase is the fundamental process of:
- Understanding why an information system should be built.
- Determining how the project team will go about building it.
Project plan
SDLC: analysisمرحلة التحليل
The system development life cycle (SDLC)
The analysis phase answers the questions of:
- Who will use the system?
- What the system will do?
- Where and when it will be used?
Investigate the current system (called the as-is system) and its problems, and the ways to design a new system (called the to-be system).
The analysis of the information produced from requirements gathering (e.g., through interviews or questionnaires), in conjunction with input from the project sponsor and many other people, leads to the development of a concept for a new system.
A system proposal
SDLC: designمرحلة التصميم
The system development life cycle (SDLC)
The design phase decides how the system will operate, in terms of:
- The hardware, software, and network infrastructure.
- The user interface, forms and reports.
- The specific programs, databases, and files that will be needed.
The design strategy is first developed to clarify:
- Whether the system will be developed by the company's own programmers.
- Whether the system will be outsourced to another firm (usually a consulting firm).
- Whether the company will buy an existing software package.
Design products and outputمنتجات التصميم ومخرجه
The system development life cycle (SDLC)
تذكّر ما يحدده كل تصميم، ثم اكشف تعريفه.
- 1Architecture designتصميم البنية
Describes the hardware, software, and network infrastructure to be used.
- 2Interface designتصميم الواجهة
Specifies how the users will move through the system (e.g., navigation methods such as menus and on-screen buttons) and the forms and reports that the system will use.
- 3Database and file specificationsمواصفات قواعد البيانات والملفات
Define exactly what data will be stored and where they will be stored.
- 4Program designتصميم البرامج
Defines the programs that need to be written and exactly what each program will do.
System specification (architecture design, interface design, database design, program design).
SDLC: implementationمرحلة التنفيذ
The system development life cycle (SDLC)
The final phase in the SDLC is the implementation phase, during which the system is actually built.
This is the phase that usually gets the most attention, because for most systems it is the longest and most expensive single part of the development process.
Two tasks in this phase:
- System construction — the system is built and tested to ensure it performs as designed.
- The system is installed, and users are trained on how to use the new system.
سؤال سريع
The system development life cycle (SDLC)
SDLC models: predictive life cycleنماذج SDLC: الدورة التنبؤية
نماذج دورة حياة تطوير الأنظمة
- Predictive Life Cycle
- Agile Software Development
Predictive life cycle
- The scope of the project can be articulated clearly, and the schedule and cost can be predicted accurately.
- The project team spends a large portion of the project attempting to clarify the requirements of the entire system and then producing a design.
Waterfall modelالنموذج الشلالي
SDLC models: predictive life cycle
A straightforward approach: it moves to another step after completing the first step properly. Every phase has its project plan, and the information is based on previous results of previous steps.
- Name: the model takes its name from the way each phase cascades into the next.
- When to use it: best used on projects where requirements have been clearly defined and agreed.
Advantagesالمزايا
- Phases are processed and completed one at a time.
- Requirements are very well understood.
- Clearly defined stages.
- Process and results are well documented.
- Suitable for small projects.
Drawbacksالعيوب
- No working software is produced until late during the life cycle.
- The testing phase at the end of the project means major defects could be undetected until late in the project, when they are more difficult to repair.
- Poor model for long and ongoing projects.
Incremental modelالنموذج التزايدي
SDLC models: predictive life cycle
Requirements divided into multiple standalone modules. Each module passes through the requirements, design, implementation and testing phases. A working version of software is produced during the first module, so you have working software early on. Each subsequent release of the module adds function to the previous release, until the complete system is achieved.
Advantages of incremental model
- Errors are easy to be recognized.
- Easier to test and debug.
- More flexible.
- The client gets important functionality early.
- Suitable for large project.
Iterative modelالنموذج التكراري
SDLC models: predictive life cycle
An iterative model does not attempt to start with a full specification of requirements. Development begins with some specifications and develops the first version of the software. If there is a need to change the software, a new version is created with a new iteration. Every release finishes in an exact and fixed period that is called iteration.
Suited to situations in which the requirements are not clearly understood and where there is a need to begin development quickly.
Advantagesالمزايا
- Help the customer identify and refine requirements and design features.
- The customer can make suggestions for possible changes to be incorporated into a further version of the software, which is then evaluated.
Disadvantagesالعيوب
- A risk is not knowing when to stop iterating.
- The iterative approach is potentially difficult to monitor and control.
Incremental and iterative togetherالتزايدي والتكراري معًا
SDLC models: predictive life cycle
Iteratingالتكرار
- Allows you to move from vague idea to realization.
- Going from rough to polished.
Incrementingالتزايد
- Is more about delivery.
The incremental and iterative models work well together. An application can be broken down into a number of increments, each of which can be implemented through a series of iterations.
سؤال سريع
SDLC models: predictive life cycle
Agile software developmentالتطوير الرشيق (Agile)
A methodology that is commonly used to deliver complex projects due to its adaptiveness. It emphasizes collaboration, flexibility, continuous improvement and high quality results.
Concept of Agile
- A way to manage a project by breaking it up into several phases.
- It involves constant collaboration with stakeholders and continuous improvement at every stage.
- Once the work begins, teams cycle through a process of planning, executing, and evaluating.
- Continuous collaboration is vital, both with team members and project stakeholders.
Core ideas of Agile
- Iterative and incremental delivery of working code.
- Frequent collaboration with stakeholders.
- Closely working.
- Self-organizing teams.
- The ability to embrace change late in the project.
The Agile Manifestoبيان Agile
Agile software development and Scrum
| Valuedمقدَّم | Overعلى |
|---|---|
| Individual and Interactions | Processes and Tools |
| Working Software | Comprehensive Documentation |
| Customer Collaboration | Contract Negotiation |
| Responding to Change | Following a Plan |
Scrumإطار Scrum
An Agile framework: a structure used to implement the ideas behind Agile project management. Its aim is to develop, deliver, and sustain complex products through collaboration, accountability, and iterative progress.
Where all the requirements needed for a viable product are listed in order of priority.
The tasks and requirements that the team need to accomplish during the next Sprint.
سؤال سريع
Agile software development and Scrum
Project management process groupsمجموعات العمليات
The project management process include:
- 1
Initiation
- 2
Planning
- 3
Execution
- 4
Monitoring & Control
- 5
Closing
Process groups can be applied to each phase of the project.
1. Initiating processesعمليات البدء
Project management process groups
Initiating processes include defining and authorizing a project or project phase.
- Prepare Project Charter, which is a document that describes the project and its goals.
- Identify stakeholders.
- Take place at the beginning of each phase.
- Re-examine the business need for the project during every phase of the project life cycle, to determine if the project is worth continuing, should be redirected, or canceled.
2. Planning processesعمليات التخطيط
Project management process groups
Planning processes include devising and maintaining a workable scheme to ensure that the project addresses the organization's needs.
| Planالخطة | Purposeالغرض |
|---|---|
| Scope plan | Define the work that needs to be done. |
| Schedule plan | Schedule activities related to the work. |
| Cost plan | Estimate cost for performing the work. |
| Quality plan | Product meets written specifications and intended use. |
| Procurement plan | Decide what resources to produce to accomplish the work. |
To account for changing conditions on the project and in the organization, project teams often revise plans during each phase of the project life cycle.
3. Executing processesعمليات التنفيذ
Project management process groups
Executing processes include coordinating people and other resources to carry out the various plans and produce the products, services, or results of the project or phase.
- Acquiring and developing the project team.
- Performing quality assurance.
- Managing stakeholder expectations.
- Conducting procurements.
4. Monitoring and controlling processesعمليات المراقبة والتحكم
Project management process groups
- Include measuring and monitoring progress against all plans to ensure that the project team meets the project objectives, stakeholder needs, and quality standard.
- Reporting performance is a common controlling and monitoring process, where project stakeholders can identify any necessary changes to keep the project on track.
5. Closing processesعمليات الإغلاق
Project management process groups
Closing processes include formalizing acceptance of the project or project phase and ending it efficiently.
- Archiving project files.
- Closing out contracts.
- Document lessons learned.
- Receiving formal acceptance of the delivered work as part of the phase.
سؤال سريع
Project management process groups
Mapping the process groups to the knowledge areasربط المجموعات بمجالات المعرفة
Project management process groups
| Knowledge areaمجال المعرفة | Initiatingالبدء | Planningالتخطيط | Executingالتنفيذ | Monitoring & controlالمراقبة والتحكم | Closingالإغلاق |
|---|---|---|---|---|---|
| Project integration management | Develop project charter | Develop project management plan | Direct and manage project work |
| Close project or phase |
| Project scope management | لا تذكر الشرائح شيئًا هنا. |
| لا تذكر الشرائح شيئًا هنا. |
| لا تذكر الشرائح شيئًا هنا. |
| Project time management | لا تذكر الشرائح شيئًا هنا. |
| لا تذكر الشرائح شيئًا هنا. | Control schedule | لا تذكر الشرائح شيئًا هنا. |
| Project cost management | لا تذكر الشرائح شيئًا هنا. |
| لا تذكر الشرائح شيئًا هنا. | Control costs | لا تذكر الشرائح شيئًا هنا. |
| Project quality management | لا تذكر الشرائح شيئًا هنا. | Plan quality management | Perform quality management | Control quality | لا تذكر الشرائح شيئًا هنا. |
| Project human resource management | لا تذكر الشرائح شيئًا هنا. | Plan human resource management |
| لا تذكر الشرائح شيئًا هنا. | لا تذكر الشرائح شيئًا هنا. |
| Project communications management | لا تذكر الشرائح شيئًا هنا. | Plan communications management | Manage communications | Control communications | لا تذكر الشرائح شيئًا هنا. |
| Project risk management | لا تذكر الشرائح شيئًا هنا. |
| لا تذكر الشرائح شيئًا هنا. | Control risks | لا تذكر الشرائح شيئًا هنا. |
| Project procurement management | لا تذكر الشرائح شيئًا هنا. | Plan procurement management | Conduct procurements | Control procurements | Close procurements |
| Project stakeholder management | Identify stakeholders | Plan stakeholder management | Manage stakeholder engagement | Control stakeholder engagement | لا تذكر الشرائح شيئًا هنا. |
سؤال سريع
Project management process groups
الخلاصة
أنهيت الدرس
الخطوة التالية: ثبّت المعلومات بالبطاقات، ثم اختبر نفسك بالأسئلة.
ما راجعته في هذا الدرس
- Project phases and the project life cycleمراحل المشروع ودورة حياته
- The system development life cycle (SDLC)دورة حياة تطوير الأنظمة (SDLC)
- SDLC models: predictive life cycleنماذج SDLC: دورة الحياة التنبؤية
- Agile software development and Scrumالتطوير الرشيق (Agile) وإطار Scrum
- Project management process groupsمجموعات عمليات إدارة المشاريع