1. PMBOK®
1.1. It is valuable approach because it enables organizations to standardize project management practices across departments.
1.2. KNOWLEGE AREAS
1.2.1. 1. Project integration management 2. Project scope management 3. Project time management 4. Project cost management 5. Project quality management
1.2.1.1. 6. Project human resource management 7. Project communications management 8. Project risk management 9. Project procurement management 10. Project stakeholder management
1.3. PROCESS GROUPS
1.3.1. 1. Initiating ---> 2.Planning---> 3.Executing---> 4.Monitoring & Controlling---> 5.Closing
2. PRINCE2®
2.1. BASED ON
2.1.1. PRINCIPLES
2.1.1.1. 1. Business Case Driven 2. Product Focus 3. Lessons Learned 4. Manage the Stage
2.1.1.1.1. 5. Adapt to the Project 6. Manage by Exception 7. Accountability
2.1.2. PROCESSES
2.1.2.1. 1.Start Project 2.Initiate Project 3.Direct Project
2.1.2.1.1. 4.Control Stage 5.Manage Product Delivery 6.Manage Stage Boundaries 7. Close Project
2.1.3. THEMES
2.1.3.1. 1. Business Case 2. Organization
2.1.3.1.1. 3. Risk 4.Quality 5. Planning
3. Leaning Cycles & Lessons learned.
3.1. 1.Understand the frame Problem
3.2. 2. Plan 3. Act 4..Reflect
3.3. LESSON LEARNED
4. WAYS TO IMPLEMENT SDLC -WATERFALL
4.1. followed in the sequential order, and so project development team only moves to next phase of development or testing if the previous step completed successfully.
4.2. Requirement Gathering and analysis −> System Design −> Implementation −> integration and Testing −> Deployment of system − > Maintenance
5. WAYS TO IMPLEMENT SDLC - AGILE
5.1. practice that helps continuous iteration of development and testing in the software development process
5.2. allows more communication between customers, developers, managers, and testers.
5.3. Themes : 1.Customer 2. Product. 3. Project Team 4. Performance
5.4. SCRUM
5.4.1. is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
5.5. XP
5.5.1. most specific of the agile frameworks regarding appropriate engineering practices for software development.
6. Proj. Methodology and the role in IT projects
6.1. Def: strategic-level plan in project management & control
6.1.1. Roles: - eliminates the need to figure things out. - provide a common language for project workers to use - provide understood roles for stakeholders, and more.
7. PLC
7.1. 3 terms for the end-of-phase review: 1. Phase Exit 2. Stage Gate 3.Kill Point These are the milestones within a project that take a look at the overall project and determine if it should be "killed".
7.2. Fast tracking occurs when a project starts one phase of development before the previous phase has completed. This can be done to reduce a schedule, but can be risky.
7.3. Phases : 1.define the project and its goals. 2.create a plan for the project, detailing objectives, resources, and controls needed for it to succeed
7.3.1. 3.execute the project plan. 4.close and keep evaluate the project