This presentation is about “Agile Project from Visibility to Closing”.
It describes the agile project from the visioning until closing.
It shows how agile concept and mindset manifests itself through agile project ‘interactions, meetings, events and producing the workable product.
2. Abdelrahman Elsheikh Bio
14 experience as Strategic PMO Director, Strategy Execution Consultant,
PMO Consultant, Project Manager, Business Analyst and Software
Engineer.
• Master Degree in Software Engineering.
• Project Management Office Certification (PMOC).
• Certified Project Management Professional (PMP).
• Agile Certified Practitioner (PMI-ACP).
• Risk Management Professional (PMI-RMP).
• Schedule Professional (PMI-SP).
• Certified Business Analyst Professional (CBAP).
• Microsoft Certified IT Professional (MCITP).
• OCP and OCA.
• Certified Professional for Requirement Engineer (CPRE).
• Certified Tester Foundation Level (CTFL).
• Earned Value Project Management (EVM).
• ISO/IEC 20000 Foundation.
• ISO/IEC 27002 Foundation.
• Certified ITIL Foundation Level.
3. Agenda
• Agile Project from Visibility to Closing Diagram.
• The Visibility of Agile Project.
• The Initiation of Agile Project.
• The Release Planning of Agile Project.
• The Inside Iteration overview of Agile Project.
• The Closing of Agile Project.
• Conclusion.
4.
5.
6. Agenda
• Agile Project from Visibility to Closing Diagram.
• The Visibility of Agile Project.
• The Initiation of Agile Project.
• The Release Planning of Agile Project.
• The Inside Iteration overview of Agile Project.
• The Closing of Agile Project.
• Conclusion.
7.
8.
9.
10.
11.
12.
13. Agenda
• Agile Project from Visibility to Closing Diagram.
• The Visibility of Agile Project.
• The Initiation of Agile Project.
• The Release Planning of Agile Project.
• The Inside Iteration overview of Agile Project.
• The Closing of Agile Project.
• Conclusion.
14.
15.
16.
17.
18. Personas
• Personas are quick guides or reminders of the key
stakeholders on the project and their interests.
21. User Stories
• User stories are often written in the following format:
– “As a <Role>, I want <Functionality>, so that <Business
Benefit>“
• Example: “As a BooksOnline customer, I want to search books
by author, so that I can more easily find books I would like to
rent.”
22. User Stories
• When developing software systems, stories should typically be
vertical slices of functionality that cut through all the relevant
architectural layers of the system, as indicated in the following
figure:
26. Affinity Diagram
• Affinity estimating is the process of grouping requirements into
categories or collections
27.
28. Product Roadmap
• A product roadmap is a visual overview of a product’s releases
and its main components.
• It is a communication tool that provides project stakeholders
with a quick view of the primary release points and intended
functionality.
29. Product Roadmap
• There is no one set way of depicting a product roadmap, but
story maps, popularized by Jeff Patton, are a commonly used
approach.
30. Product Roadmap
• Story maps help select and group features for a release.
• These diagrams show the sequence of the features and
indicate their importance to the project by classifying them as
“backbone,” “walking skeleton,” or additional features.
31. Product Roadmap
• All systems have some essential functionality that they need to
perform.
• This essential functionality makes up the backbone of the
system.
32. Product Roadmap
• The walking skeleton describes the smallest system that could
possibly work.
• Finally, any remaining features hang below the walking
skeleton and are prioritized by their importance to the system.
33. Product Roadmap
• Once the features are placed on the map according to their
importance and sequence, the customer’s priorities are
balanced with the team’s capacity to deliver, and the releases
that will make up the product roadmap are identified.
34. Product Roadmap
• See the following diagram for an example of a product road
map showing the first, second, and third release:
36. Product Roadmap
• Using this approach, the final product roadmap consists of
collections of story maps and shows what will go into each
release.
37. Agenda
• Agile Project from Visibility to Closing Diagram.
• The Visibility of Agile Project.
• The Initiation of Agile Project.
• The Release Planning of Agile Project.
• The Inside Iteration overview of Agile Project.
• The Closing of Agile Project.
• Conclusion.
43. Story points
• Story points are a unit of measure for expressing an estimate of the
overall effort that will be required to fully implement a product
backlog item or any other piece of work.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55. Agenda
• Agile Project from Visibility to Closing Diagram.
• The Visibility of Agile Project.
• The Initiation of Agile Project.
• The Release Planning of Agile Project.
• The Inside Iteration overview of Agile Project.
• The Closing of Agile Project.
• Conclusion.
73. Agenda
• Agile Project from Visibility to Closing Diagram.
• The Visibility of Agile Project.
• The Initiation of Agile Project.
• The Release Planning of Agile Project.
• The Inside Iteration overview of Agile Project.
• The Closing of Agile Project.
• Conclusion.
74.
75. Agile Project Closure Activities
• Handing Over to Operations
• Tidying Up Any Loose Ends
• Reviewing the Project
• Celebrating
• Going Home
76. Agenda
• Agile Project from Visibility to Closing Diagram.
• The Visibility of Agile Project.
• The Initiation of Agile Project.
• The Release Planning of Agile Project.
• The Inside Iteration overview of Agile Project.
• The Closing of Agile Project.
• Conclusion.
85. Agenda
• Agile Project from Visibility to Closing Diagram.
• The Visibility of Agile Project.
• The Initiation of Agile Project.
• The Release Planning of Agile Project.
• The Inside Iteration overview of Agile Project.
• The Closing of Agile Project.
• Conclusion.