Week 2 Class Rev3 PDF

Professional Practice & Standards WEEK 2 DR MUATH ABU ARQOUB, PMP BOND UNIVERSITY Project Management Methodologies Adaptive Critical Path Agile PRINCE2 Project PRiS...

Professional Practice & Standards WEEK 2 DR MUATH ABU ARQOUB, PMP BOND UNIVERSITY Project Management Methodologies Adaptive Critical Path Agile PRINCE2 Project PRiSM Method Framework Critical Chain Project PMI PMBOK Scrum Kanban Spiral Management Rapid Extreme Application Six Sigma Waterfall Lean Programming Development Packaged Rational New Product Outcome Enabled Crystal Unified Introduction Reengineering Mapping Process What is project management? 1. What problem are you solving? 2. How are you going to solve this? 3. Whats your plan? 4. How will you know when you are done? 5. How will did the project go? Project Life Cycle Project Management Methodologies Adaptive Critical Path Agile PRINCE2 Project PRiSM Method Framework Critical Chain Project PMI PMBOK Scrum Kanban Spiral Management Rapid Extreme Application Six Sigma Waterfall Lean Programming Development Packaged Rational New Product Outcome Enabled Crystal Unified Introduction Reengineering Mapping Process What is agile? Agile is a family of product development methodologies in which customer requirements and solutions evolve through repeated cycles of planning, collaboration, and delivery Agile talks about the Agile manifesto which came out in 2001 Project that are consistent with Agile manifesto are called agile projects Less emphasis on deterministic planning and more emphasis on adapting to change Short-term plans Makes it useable as fast as possible Would you use Agile to build a house? Incremental and iterative Gives you an insight of the whole picture and the customer’s priorities very quickly Japanese ideas like Kaizen began to appear in the form of retrospectives The entire team regularly discusses what worked and what did not in an iteration Definition of Agile: Explained Iterative and incremental Developing in a measured fashion where each increment is built on the last iteration Highly collaborative Encouraging the team interaction and engagement Self-organizing teams Recognizing the team’s competence of finding the right solution to deliver value Just enough ceremony Creating only those documents that justifies the requirement, meetings with defined lengths, frequencies, and goals. High-quality software Reflecting the importance of quality in the agile delivery model Meets the changing needs of its stakeholders Emphasizing the willingness of agile to adapt to change and embrace it The Agile Manifesto  Individuals and Interactions Over Processes and Tools The Agile Manifesto Collaboration, individuals, and their interactions are more Explained critical than well-defined processes and complex tools Agile helps team members interact through techniques like co-location and daily stand-up meetings  The Agile Manifesto Explained Working Software Over Comprehensive Documentation Documentation does not demonstrate real progress or value A working software or solution is an effective measure of progress that a business can see and provide feedback on The Agile Manifesto Explained Customer Collaboration over Contract Negotiation Organizations need to be flexible and accommodating rather than following the definitions of contracts Constant collaboration with customers to accommodate changes are more important than adhering to formal contracts  Responding to Change Over Following a Plan Agile emphasizes responding to change than being constrained by a detailed plan The Agile Manifesto It is recommended to bring the project back Explained on track by responding to change and refining the plan instead of sticking to the original plan Agile encourages teams to spend more time working than creating project plans  less waste and reduced cost of rework – Higher productivity and developing what is absolutely essential lower cost for the customer Improved Stakeholder Greater adaptability to changes in the market Satisfaction Stakeholder will see the whole picture Rapid Feedback earlier Benefits of Agile Faster Time to Market incremental delivery – reduced cost of delay – more business value Clear Set of Acceptance Clear definition of done – clear acceptance criteria for a story Criteria Improved Employee Self organization - Improved employee - job satisfaction due to sustainable pace Engagement Project Life Cycle Characteristics https://eternalsunshineoftheismind.wordpress.com/2013/02/04/agile-methods-of-software-development-2/ PMBOK’s Process