AGILE PROJECT MANAGEMENT

SOFWARE DEVELOPMENT APPROACHES

 WATERFALL: sequential development till the end

 AGILE: incremental or iterative development model/framework, where
application is developed in small chunksor bit by bit
o Kanban
o DSDM
o XP
o Agile: Agile is iterative or incremental framework /model.
 Manifesto developed by 17 developers in 2001
 Values (4)
o Individual and interactions over process and tools
o Working software over comprehensive documentation
o Customer collaboration over contract negotiation
o Responding to changes over following a plan
 Principles (12)
o Customer Satisfaction through Continuous Delivery
o Welcome Changing Requirements
o Deliver Working Software Frequently
o Build Projects around Motivated Individuals
o Face-to-Face Communication
o Working Software as the Primary Measure of Progress
o Maintain a Sustainable Pace
o Continuous Attention to Technical Excellence
o Simplicity
o Self-Organizing Teams
o Reflection and Adaptation

SCRUM

Lightwieght framework that hepls teams or organizations generate value through adaptive solution for
a complex problem. Development framwork Used in:

 Low risk project

 Tiny project
 Independent team
 Low complexities
 No sub team

For complex projects, use SCRUM of SCRUM. That is, there are scrum team in a scrum team.

Sprint: is an iteration (in Agile) or a timeframe/timebox during which development occurs usually
less than a month.

SCRUM projects encourage:

  Self-management and communication
 Continuous improvement
 Frequent work inspection
 Adapt and optimize build

SCRUM VALUES (FROCC)

 Focus: on the goal

 Respect: opinion of other, trust their capabilities, even respect to stakeholder by listening
 Openness: about work, challenge, need for collaboration
 Courage: members should have courage to make decisions and attack problems
 Commitment: to the goal

SCRUM PILLARS (TIA)

 Transparency e.g. product backlog, Daily stand up, Retrospective meetings

 Inspection e.g. SCRUM Board, Sprint review
 Adaptation

BENEFITS OF SCRUM

 Project can respond easily to change

 Problems are identified early
 Customer gets most beneficial work first
 Work done will better meet customer needs
 Low bureaucratic overhead

SCRUM TEAM

 Characteristics of SCRUM Team

o Share the same norms and rules.
o Collective accountability for delivery.
o Empowered team (Self-managing)
o Autonomous as much as possible.
o Cross-functional
o Small and has no sub-teams (Ideally 10 or less).
o Full-time work
o Co-location
 Responsibilities of SCRUM Team
o Breakdown requirements, create tasks and distribute them
o Perform Daily Sprint Meeting
o Ensure that Potentially Shippable functionality is delivered at sprint end
o Update status of remaining effort to allow
COMPONENTS OF SCRUM

 SCRUM ROLES
o Product Owner: One who tell the team what to develop. Most of the roles of the
classical product and project manager are combined within this role. Bigger project may
have more than one PO. Scrum of Scrum is a technique to connect multiple teams to
deliver complex solutions.
 Product Owner items
 Product Strategy
o Product Strategy: Meant to describe the vision to be
accomplished. Strategies to deliver product.
 Vision: Future state
 Value: What puts smile of the face of customer
 Validation:
 Product validation: Customer feedback, sprint
review
 Process validation: Retrospectives
 Product Roadmap
 Product Backlog
 Business Case
 Responsibilities
 Manage Scrum Backlog – Create, Maintain, Prioritize, Describe
o Own product on behalf of the company, make appropriate
decision and responsible for product delivery including MVP
(First form of product that can be released to the user with core
functions)
o Managing and expressing business and functional expectations
o Create and communicate product vision, strategy and roadmap
to team and decide official releases
o Ensure members understand what is required
o Checking and accepting sprint results
o Ensure right work is done at right time
o Monitor progress and leading team
 Release Management – Create release plan, decide deliveries
 Stakeholder Management:
o Use RACI (Responsible, Accountable, Consulted, Informed)
Matrix and Power influence Grid to engage them
o Engage with them early and often (weekly meeting with key
stakeholders, SMEs: weekly, finance: once a month
recommended)
o Remain thoughtful and sincere
o Make it easy to understand you. Avoid big grammar to impress
o Be sensitive to stakeholders dynamics
o Make them fee important to prevent rejection
 o Make business case very clear and specify benefit to
organization
o Generate Stakeholder Buy-in
 Involve them in process, decision making etc. the more
involve they are, the more they will invest
 The need of those controlling finances must be seen
and addressed
o Scrum Master: Takes care of impediments. Facilitate Scrum. As per Crum Guide, he is
the servant leader.
 Guide, coach Scrum Team on proper use of scrum
 Facilitate SCRUM events - Daily standups, Sprint review, Retrospective.
 Remove impediments and external requests, instead act as change agent to
direct people to the right channel.
 Ensure efficient communication between SCRUM team and PO.
 Motivate team and engage in team building excercise
o Development Team: Develop the product.
 Developers are the people in the Scrum Team that are committed to creating
any aspect of a usable Increment each Sprint
 SCRUM Events/Ceremonies
o Sprint planning
o Daily Sprints/Standups (Report what I did yesterday, what I’m doing today and Any
impediment or blockage)
o Sprint review
o Retrospectives
 SCRUM Artefacts
o Sprint Burndown Diagram
o DoD
o Crum Board
o Sprint Backlog
o Product Backlog

Sprint release

PSI