Agile Software Development

• Highest priority for customer satisfaction

thro early and continuous delivery
• Welcome changing requirements, even late
in development As a user, I want to cancel

• Deliver working software frequently my reservation, so that I

can get refunded..

• Business team and developers must work As a user, I want to View
Room Photos, so that I
together throughout the project can see the room before
booking.
As a user, I want to View
Hotels with Rooms
Available, so that I can
save time while booking.
Backlog
As a user, I want to
cancel a reservation, so
that I can get refunded.
As a user, I want to
reserve a hotel room,
so I can plan my stay.
Small cycles of Product
development Increment
 Scrum
• Scrum refers to a holistic or “rugby” approach—where teams go the distance as a
unit, passing the “project ball” back and forth—as opposed to the traditional
sequential or “relay race” approach for managing new product development.

The entire team works to move

the ball down field as a unit
 Scrum vs. Waterfall Development
Waterfall Requirements Design Code Test

time

Rather than doing all of one thing at a

time…
…Scrum teams do a little of everything all
the time.

Scrum User Stories

time
 Scrum Activities by PMO phases
Initiate Phase Plan Phase Execute Phase

Identify User Story

Product Owner Workshop

Commitment
from Product
Owner Sprint
Release
Planning Sprint Daily Backlog Sprint Sprint
Planning Scrum Grooming Review Retrospective

Product Backlog Sprint Backlog Production-

Ready Increment

Project Metrics
 Scrum Roles

Product Owner Scrum Master Development Team

 Product Owner
• Defines the vision, features for a product
• Responsible for ROI
• Makes scope vs. schedule decisions
• Prioritizes the product backlog
• Involved every day
• Reviews with stakeholders
• Application Teams: Typically the manager or business analysis
 Scrum Master
• Responsible for enacting Scrum process
• Remove impediments for team
• Shield team from external interference
• Coaches the team to their best possible performance
• Helps team improve their productivity
 The Development Team
• Ideally 3 to 9 members
• Cross functional –
• Developers, Testers, Analysts, Architects, UX designers, etc.
• Members should be full time
• Maybe exceptions (e.g. DB administrator, Network Engineer, etc.)
• Responsible for commitments
• Teams are self organizing
 Product Backlog
As a user, I want to reserve a hotel
room, so I can plan my stay.

• Prioritized list of User Stories for building the As a user, I want to cancel my
product reservation, so that I can get refunded..

• Single source of User Stories As a user, I want to View Room Photos,

so that I can see the room before

• Product Owner responsible for Backlog booking.

As a user, I want to View Hotels with

• Never complete, evolves with product and Rooms Available, so that I can save time
while booking.
environment
• User Story will have Size, Priority, Business ?

Value, Acceptance Criteria and Risks

?

Product Backlog
 User Stories
• They shift the focus from written to verbal communication
• They are written in business language so users can understand and
prioritize them
• They describe relatively small pieces of functionality that delivers
business value
• They avoid implementation detail
• Communicating software requirements is a challenging effort
• User Stories facilitate the conversations that need to take place
Questions?
Project Integration management &
Project Planning process
 PMBOK
Project
management
processes
 PMBOK
Project
management
processes
Project Integration Management processes

• Develop Project Charter : The process of

developing a document that formally authorizes the
existence of project and provides PM authority to
apply resources for project activities
• Develop Project management plan : The
process of defining, preparing & coordinating all
subsidiary plans & integrating them into
comprehensive project management plan
• Direct and Manage project work : The process
of leading and performing work defined in the
project management plan & implementing
approved changes
Project Integration Management processes

• Monitor and control project work : The process

of tracking, reviewing and reporting project
progress against the performance objectives
defined in Proj Mgt plan
• Perform integrated change control : The
process of reviewing all change requests, approving
changes and managing changes of deliverables,
organizational process assets, project documents,
and other project management plans
• Close project or phase : The process of finalizing
all activities across all of the project management
process groups to formally complete the phase or
project
 Project Charter
• Develop Project Charter :
The process of developing a
document that formally
authorizes the existence of
project and provides PM
authority to apply resources
for project activities.
It comprises of :
• Authorization of project
• Defines business needs
• Identifies sponsor of the project
• Identifies the project manager
• Assigns authority to Project manager
on behalf of project Sponsor
 Project Charter

• Elements of Project Charter :

• Official project name
• Project Sponsor & PM’s name and contact details
• Purpose of the project
• Business case for project
• Basic timeline/schedule
 Project Charter

• Inputs for Project Charter :

• Enterprise environment factors like culture
• Formal Project contract details & SoW
• Purpose of the project/Business case
• Organizational process assets e.g., lessons learnt from the past projects
PROJECT CHARTER

Exercise 2 : Develop a project Charter for the Mumbai Metro project for developing and
deployment of 200 objects on Java Full stack/.NET