PROJECTCON | AGILECON Midwest 2019 in Indianapolis on May 10, 2019
Presenter: DJ McCord
The Agile PMP: What PMPs need to know to compete in today's market
Agile is not a buzz word. Agile is here to stay. If you organization has not yet adopted Agile in some way, shape, or form, it will soon. In 2018, PMI added Agile to the PMBOK and the PMP exam. This session will discuss why it is critical that PMPs understand what Agile is, how a PMP can improve their marketability, the new Agile content added to the PMBOK, how a PMP can learn the new Agile content included in the PMBOK, and what certifications a PMP can obtain to make them a triple threat in the industry.
Attendees will learn:
An overview of Agile
Why PMPs need to know Agile
Agile additions to the PMBOK 6th Edition
How a PMP can re-up their certification to include Agile
What combination of certifications a PMP should hold to gain a competitive advantage
Event Website: https://projectconevent.com
LinkedIn: https://www.linkedin.com/company/projectcon-llc
Facebook: http://www.facebook.com/ProjectConEvent
Twitter: http://www.twitter.com/projectconevent
YouTube: https://www.youtube.com/channel/UCLLG1SGPs1L5YLoFndvGGhQ
Instagram: https://www.instagram.com/projectconevent
Presentation Slides: https://slideshare.com/projectcon
Post Event Trailer: https://youtu.be/1_RzFBnZ7bo
ProjectCon AgileCon Project Management
7. Agile Principles
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
2. Welcome 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 time scale.
8. Agile Principles
4. Business people and developers must work together daily
throughout the project.
5. Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the
job done.
6. The most efficient and effective method of conveying information
to and within a development team is face-to-face conversation.
9. Agile Principles
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
9. Continuous attention to technical excellence and good design
enhances agility.
10. Agile Principles
10. Simplicity – the art of maximizing the amount of work not done
– is essential.
11. The best architectures, requirements, and designs emerge from
self-organizing teams.
12. At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
11. Roles
• Product Owner / ‘Customer’:
• Serves as the ‘Voice of the End User’
• Maximizes the value of the product by choosing the features /
components to be worked on
• Optimizes the work of the Development Team
12. Roles
• Agile Coach [e.g.: Scrum Master]
• Functions as a ‘Servant Leader’ for the Team
• Trains and mentors Team Members as to principles and
practices of Scrum
• Assists and advises Team as it self-organizes and self-
manages
• Facilitates Team meetings, while training Team Members
to facilitate meetings themselves
13. Roles
• Development Team:
• Self-organizes to plan and execute work on Stories within Sprints
[Iterations]
• Self-manages as Sprints progress, and makes decisions about the
tactics of work accomplishment
14. Roles
• Specific Development Team Roles:
• Tracker: Evaluates and communicates progress against the plan
• Tester: Translates the acceptance criteria into actual test cases; executes
the acceptance tests, and communicates the results
• Analyst: Helps the Customer describe the Features in terms the Developers
can relate to, and act on
15. Planning Components
• Product Vision – similar to a Business Case
• Product Roadmap – similar to a Project Scope Statement
• Product Backlog – similar to a WBS
• Release Plan – similar to a Milestone Chart
• Iteration Plan – similar to a Project Network Diagram [PND]
• Features – similar to deliverables
• Tasks – similar to activities
17. Customer Interface
• Emphasis on “daily” interaction with “business people”
• Focus person is the Product Owner
• Input of ideas / requests from stakeholder goes into Product Backlog
• Formal ceremony for review of completed Features is the Product
Review Meeting after each Iteration
• Agile welcomes and encourages changing requirements, even late in
the project
• Ultimate objective of the Agile project is delivering value to the
Customer
19. New Attitudes
• Embrace Uncertainty
• Empower Team Members
• Embrace Change
• Display Flexibility
• Enhance Transparency and Openness
• Let the Customer Guide the Progress
• Leverage the Product Delivery for the Organization’s Competitive
Advantage