Chapter 10 Agile Retrospectives: Meiktila University of Economics

MEIKTILA UNIVERSITY OF ECONOMICS
Master of Development Studies Programme

MDevS (1st Batch),2nd year (2019-2020)
NAYPYITAW
Project Evaluation and Lessons Learned
Chapter 10 Agile Retrospectives

Professor- Dr.Thin Thin Oo
14-3-2020 Presented by Group-9

1
Participants of Group-9 (MDevS-II)
(2019-2020)
 Mg Pyae Phyo Ag Sr.no(7)

 Ma Nwe Ni Ag Sr.no(6)
 Ma Sandar Ag Sr.no(8)
 Ma Win Win Aye Sr.no(16)
 Ma Ohn Mar Hlaing Sr.no(19)
 Ma Khin Ohnmar Lwin Sr.no(35)
 Ma Khine Khine Shwe Sin Sr.no(68)
 Ma Naw Cho Cho Win Sr.no(79)
2
WHAT ARE AGILE RETROSPECTIVES?(ARs)
Agile Retrospectives(ARs) are such as software.

Lessons Learned (LL) (ideas, discussions, and documentation)
into development processes
Project teams set aside time to reflect on or document how the team is
performing: what is being done right, wrong, and can be done differently.
ARs are frequently ongoing and at the end of the project. ARs may include
key stakeholders (i.e., vendor sand suppliers) and sponsors as well as designated
clients who may be involved in project learning, such as observations that occur,
during the process of user acceptance testing.
3
 Agile Retrospectives (ARs) have been described as the heartbeat of Scrum
 Scrum is an incremental and iterative development framework for Agile software
development.
 Scrum is founded on flexible change management principles that enable revisions
to processes based on the need of a project team.
 The Scrum Master as required to support change immediately.
 In Agile software development, it is common for programming and coding
requirements to become more refined through collaboration.
4
A BRIEF HISTORY OF AGILE PROJECT MANAGEMENT
Agile Project Management has a relatively new introduction into the marketplace.
We are uncovering better ways of developing software by doing it and helping others do
it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
5
V-model
Concept Deploy
Requirement Test
Designs Integrate
Develop
The benefits of Agile Project Management include

 Increased team performance
 Improved product control
 Better overall team performance
 Enhanced quality
 Streamlined processes
 Reduction in documentation as a result of streamlined processes
 Decreased cycle time for deliverables
 Effective process for managing risk
 Flexible change management
 Focused prioritization of specific requirements
 Leaner approaches to resource utilization 6
Agile Project Management
 Hardware Products
 Construction
 Art
 Landscape
 Music
 Movies
 Cooking and Culinary
 Hospitality
7
According to Layton (2012) Model
Agile Project are built on
• Transparency:
• Frequent Inspection:
• Adaptation:
CMMI is easily understood by looking at the attributes of the maturity levels:
Level 1: Initial—Processes are unpredictable , poorly controlled, and reactive.

Level 2: Managed—Processes are characterized for projects and are often reactive.
Level 3: Define—Processes are characterized for the organization and are proactive.
Level 4: Quantitatively Managed—Processes are measured and controlled.
Level 5: Optimizing: Focus is on process improvement.
8
Important Agile project Management Retrospectives Concepts to
Understand
Agile Project that involved
 Developing knowledge management systems

 Human resource information systems
 Laboratory information management
9
Important Agile project Management Retrospectives Concepts to
Understand
1. Understand the mindset of the people you are working with

2. Consider project documentation needs to be streamlined.
3. Keep in mind ARs need to be concise.
4. ARs need to be communicated at the right time.
5. ARs need to be communicated at the right place.
6. ARs need to be communicated to the right people.
7. ARs need to be communicated in the right way.
8. Bear in mind that ARs should be scheduled.
9. Make ARs enjoyable.
10. ARs frequently require a mixed-method approach.
10
THANK YOU
11

Chapter 10 Agile Retrospectives: Meiktila University of Economics

Uploaded by

Copyright:

Available Formats

Chapter 10 Agile Retrospectives: Meiktila University of Economics

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 10 Agile Retrospectives: Meiktila University of Economics

Uploaded by

Copyright:

Available Formats

MEIKTILA UNIVERSITY OF ECONOMICS

Master of Development Studies Programme

Project Evaluation and Lessons Learned

Chapter 10 Agile Retrospectives

14-3-2020 Presented by Group-9

 Mg Pyae Phyo Ag Sr.no(7)

Agile Retrospectives(ARs) are such as software.

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

The benefits of Agile Project Management include

CMMI is easily understood by looking at the attributes of the maturity levels:

Level 1: Initial—Processes are unpredictable , poorly controlled, and reactive.

Agile Project that involved

 Developing knowledge management systems

1. Understand the mindset of the people you are working with

You might also like