Introducing
Your new presentation assistant.
Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.
Trending searches
Project Managment Playbook
Aaliyah Ichino
Waterfall
Waterfall methodology is a sequential approach that divides the SDLC to distinct phases such as requirements gathering, analysis and design, coding and unit testing, system and user acceptance testing, and deployment.
The next phase can only proceed if the previous phase has been completed. In between phases, a deliverable is expected or a document is signed off.
Agile
Agile methodology is a team-based approach that emphasizes rapid deployment of a functional application with a focus on customer satisfaction.
It defines a time-boxed phase called a sprint with a defined duration of two weeks.
Hybrid
Hybrid methodology is the combination of Waterfall and Agile methodologies.
Everyone knows what they are in for because the project size, timeline and costs are determined from the get-go.
Everything is documented in detail along the way. So, if your suddenly short a developer it shouldn’t have an impact on the project.
Detailed documentation, makes it easier to improve your software if you plan to do so in the future.
You can adjust and iterate requirements along the way.
It’s also quite easy to add or delete features as the project moves along.
Bugs are caught and fixed early on.
Clients can give input at the end of each sprint rather than wait until the entire project is finished.
The goal of a hybrid method is to be able to both define the requirements up front (planning, budgeting, etc.) as with a waterfall approach, and then to move onto an agile approach when it comes to design, development and testing.
Focus:
Technical processes, inputs, tools and techniques, and outputs for the project manager
1. Initiating
2. Planning
3. Executing
4. Monitoring & Controlling
5. Closing
1. Project Integration Management
2. Project Scope Management
3. Project Schedule Management
4. Project Cost Management
5. Project Quality Management
6. Project Resource Management
7. Project Communications Management
8. Project Risk Management
9. Project Procurement Management
10. Project Stakeholder Management
Focus:
Skills and resources for the team to deliver value-based outcomes
1. Stewardship: Be a diligent, respectful, and caring steward.
2. Team: Create a collaborative project team environment.
3. Stakeholders: Effectively engage with stakeholders.
4. Value: Focus on value.
5. Systems thinking: Recognize, evaluate, and respond to system interactions.
6. Leadership: Demonstrate leadership behaviors.
7. Tailoring: Tailor based on context.
8. Quality: Build quality into processes and deliverables.
9. Complexity: Navigate complexity.
10. Risk: Optimize risk responses.
11. Adaptability and resilience: Embrace adaptability and resiliency.
12. Change: Enable change to achieve the envisioned future state.
1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan
1. The highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. The project team welcomes changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. The process builds projects around motivated individuals, giving them the environment and support they need, and trusts them to get the job done.
6. A face-to-face conversation is the most efficient and effective method of conveying information to and within a development team.
7. Working software is the most important measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should maintain a constant pace indefinitely.
9. Pay continuous attention to technical excellence, and good design enhances agility.
10. Simplicity is essential. This is the art of maximizing the amount of work not done.
11. Self-organizing teams produce the best architectures, requirements, and designs.
12. At regular intervals, the team reflects on how to become more effective and adjusts its behavior accordingly.
Lean methodologies can eliminate waste, the non-value-added component of anu production process.
When applied properly, lean generates huge improvements in efficiency, cycle time, productivity, materials costs, and scrap.
This lowers costs and improve competitiveness.
The Cynefin Framework was developed by David J. Snowden in 1999.
It aims to help leaders understand that every situation is different and requires a unique approach to decision making.
The framework outlines five situational domains (clear, complicated, complex, chaotic and confused) that are defined by cause-and-effect relationships.