Agile-Scrum Practices

Sharing
& Acknowledgement For Basel II Project of VPBank

@: Do Manh Quan
Agenda

 Agile Sharing
Traditional Software Development
Agile Principles
Agile – Scrum Framework keys
 Basel II ‘s Agile-Scrum
Where we are being?
Change or next Action
Agenda

 Agile Sharing
Traditional Software Development
Agile Principles
Agile – Scrum Framework keys
 Basel II ‘s Agile-Scrum
Where we are being?
Change or next Action
Traditional Software Development - Waterfall
Traditional Software Development - Waterfall

Fit when
Customer knows all reqs upfront
Requirements are stable
Technologies are well known and mature
All problems have been solved before
Traditional Software Development - Waterfall

The facts
Client doesn’t know what they want
Requirements are NOT stable
We thought we knew how but we’re wrong
Many external factors affect to the objectives
Agenda

 Agile Sharing
Traditional Software Development
Agile Principles
Agile – Scrum Framework keys
 Basel II ‘s Agile-Scrum
Where we are being?
Change or next Action
Agile Principles - 1
Agile Principles - 2

Agile emphasized
Collaborate between the development team and
business experts.
Face-to-face communication
Frequent delivery of deployable business value
Tight and self-organizing teams
Agile Principles - 3

Agile advantages
Customer has frequent and early deliveries
Customer gains a strong sense of ownership by
working with project team.
More quickly produce a basic version of working
software
Focus to development, direct to the customer
Agile – Some methods
 Scrum
 Extreme Programming
 Adaptive Software
Development (ASD)
 Dynamic System
Development Method
(DSDM)
 Lean Software Development
 Lean/Kanban
…
Agenda

 Agile Sharing
Traditional Software Development
Agile Principles
Agile – Scrum Framework keys
 Basel II ‘s Agile-Scrum
Where we are being?
Change or next Action
What is Scrum ?

Scrum is a framework for developing complex products

and systems.

It is grounded in empirical process and control theory.

Scrum employs an iterative and incremental approach to

optimize predictability and control risk.
- Ken Schwaber
Keypoints of Scrum - 1

Scrum is for incremental product developments

Scrum provides a structure of roles, meetings, rules and
artifacts
Teams are responsible for creating and adapting their
processes.
Scrum uses fixed-length iterations called Sprint, typically
2 weeks to 4 weeks long.
Build a potentially shippable product increment every
sprint
Keypoints of Scrum - 2
Keypoints of Scrum - 3
Limitations:

Teams: 7 (+/- 2) members

A Sprint: Duration 2-4 weeks.
Meetings: Daily Scrum Meeting, Sprint
Planning, Sprint Review, Sprint
Retrospective, Sprint Refinement Meeting.
Keypoints of Scrum - 4
Roles :

 Product Owner
 Scrum Master
 Development Team
 Stakeholders
 Managers
Keypoints of Scrum - 5
Responsibilities :
 Product Owner:
 Single person for maximizing the return on investment.
Responsible for product vision.
Decides whether to ship
Decides whether to continue development
Has a leadership role
Write user stories and help others write
Understand the business value of each user story and prioritize the
user stories into ordered backlog
...
Keypoints of Scrum - 6
Responsibilities :
 Scrum Master:
 No management authority
 Leadership role, mentoring, coaching, …
 Helping problem solve, ensuring Scrum is understood and
enacted, adhered to Scrum theory, practices, and rules.
 Providing creative input, and guiding the skills
development of teams members
Keypoints of Scrum - 7
Responsibilities :
 Development Team: They are
 Self-organizing
 Cross-functional
 Decide “what to commit to”
 No titles for Development Team members
Keypoints of Scrum - 8
Rules:
 Daily Scrum: <15 minutes, just 3 things: done yesterday, do today and
issues. Only one place, at one time
 Sprint:
 Fixed period of time.
NO CHANGE: what commited to deliver, the GOAL in a Sprint.
 Product Owner:
 Single person for maximizing the return on investment.
Responsible for product vision.
Agenda

 Agile Sharing
Traditional Software Development
Agile Principles
Agile – Scrum Framework keys
 Basel II ‘s Agile-Scrum
Where we are being?
Change or next Action
Basel II Scrum: Discussion

 Scrum Teams ?
 Who is PO ? Who is Scrum Master ?
And what’ re their’ roles ?
 What meetings have we followed ?
 What rules have we followed ?
 ….
Questions
&
Answers