Agile project management is an iterative method of determining requirements for engineering and information technology development projects in a highly flexible and interactive manner. One difference between agile and iterative development is that the delivery time in agile is in weeks rather than months. Both iterative and Agile methodologies were developed as a reaction to various obstacles that developed in more traditional project management. For example, as technology projects grow in complexity, end users tend to have difficulty defining the long term requirements, without being able to view progressive prototypes. Projects that develop in iterations can constantly gather feedback to help refine those requirements.
2. www.iactglobal.in
Agile / Agile Software Development
• Dictionary Meaning of Agile
– Moving Quickly and Lightly / Nimble
• Agile Software Development
– Is a group of software development methods based on iterative and
incremental development, where requirements and solutions evolve through
collaboration between self-organizing, cross-functional teams.
– It promotes adaptive planning, evolutionary development and delivery, a
time-boxed iterative approach, and encourages rapid and flexible response to
change.
3. www.iactglobal.in
Agile Certified Practitioner (PMI-ACP®)
• Project Management Institute (PMI) (http://www.pmi.org)
In response to the growing relevance of Agile methodology for all
Project Managers, the Project Management Institute (PMI®) has
begun offering the Agile Certified Practitioner (PMI-ACP®)
certification exam, since 2012.
5. www.iactglobal.in
Exam Content Outline
• Computer Based Testing (CBT) mode only @ Prometric Centers.
• Comprised of 120 multiple-choice questions
– With 20 of those questions considered "pretest questions
– "Pretest questions will not affect the score and are used in examinations as an effective
and legitimate way to test the validity of future examination questions.
• Allotted time Three (3) hours
• No Negative Marking
• Passing Criteria ???
6. www.iactglobal.in
Exam Content Outline – Domain Split
• Domain I : Value-Driven Delivery
• Domain II : Stakeholder Engagement
• Domain III : Boosting Team Performance Practices
• Domain IV : Adaptive Planning
• Domain V : Problem Detection and Resolution
• Domain VI : Continuous Improvement (Product, Process, People)
7. www.iactglobal.in
Basic Concepts of Project Management
PROCESS
• A process is a collection of interrelated work tasks initiated in response to an event
that achieves a specific result for the customer of the process.
• A process is a series of steps and decisions involved in the way work is completed.
8. www.iactglobal.in
Project Vs. Operation
PROJECT
• A project is a temporary endeavor undertaken to create a unique product, service, or
result.
• The temporary nature of projects indicates a definite beginning and end.
• A project can involve a single person, a single organizational unit, or multiple
organizational units.
• Example: Construction of house, new product, new services, new document etc.
OPERATION
• Operations are the ongoing execution of activities that produce the same output, or
provide a repetitive service, don’t produce anything new, but they are necessary to
maintain and sustain the system.
• Operations are permanent in nature, and their only constraint is to make profit for the
organization.
• Example: A manufacturing or production unit.
Few Similarities:
- Performed by people
- Constrained by limited resources
- Planned, executed, and controlled
9. www.iactglobal.in
Program & Portfolio
PROGRAM
• A Program is a group of
related projects managed
in a coordinated way to get
benefits and control not
available from managing
them individually.
PORTFOLIO
• Portfolio refers to the
group of related or non-
related projects, or
programs.
• A portfolio may consist of
several non-related
projects without having a
single program.
10. www.iactglobal.in
Projects Management Office (PMO)
Is an organizational body or entity assigned various responsibilities related to the
centralized and coordinated management of those projects under its domain.
14. www.iactglobal.in
Life Cycle Models - Waterfall
Advantages
The Waterfall method is also well known amongst
the software developers therefore it is easy to use.
Works well for smaller projects where requirements
are very well understood.
Cost effectiveness - time spent early in the software
production cycle can lead to greater economy at later
stages.
Disadvantages
The crucial disadvantage of this model is that testing
is understood as a “one time” action at the end of the
project just before the release the operation.
The test is seen as a “final inspection”, an analogy to
a manufacturing inspection before handling over the
product to the customer.
High amounts of risk and uncertainty.
Inflexible .
Poor model for complex and object-oriented
projects.
15. www.iactglobal.in
Life Cycle Models - Iterative
Advantages
Building and improving the product step by step. Hence can track the defects at
early stages. This avoids the downward flow of the defects.
In iterative model can get the reliable user feedback. When presenting sketches
and blueprints of the product to users for their feedback.
Less time is spent on documenting and more time is given for designing.
Disadvantages
Each phase of an iteration is rigid with no overlaps.
Costly system architecture or design issues may arise because not all requirements
are gathered up front for the entire lifecycle.
Difficult to obtain customer feedbacks.
16. www.iactglobal.in
Life Cycle Models - Incremental
Project delivery is divided into elements
(analyze, design, code, test and release)
Advantages
Quick feedback loop from business
stakeholders.
Focus on customer feedback.
Customers feels the product early.
Disadvantages
Scheduling of the development is difficult
with incremental model.
Tracking and monitoring is difficult.
Testing needs to be exhaustive in each
component/part.
17. www.iactglobal.in
Agile – the ADAPTIVE Life Cycle Model
The main difference of
this and other two
approaches of
development is that
this Agile lifecycle
focuses on continual
changing by
interacting with its
customers to refine
and finalize the
product while also
checking if the
product is becoming
what their customer
has been waiting for.