Agile project management with scrum

Wednesday, September 6,
2017
1

Wednesday, September 6,
2017
2
Tawfiq Mohammad Abdus Sattar
Manager – Software
ERA-InfoTech Limited
Dhaka, Bangladesh
A skilled IT Professional having 12 years (+)
experiences with Banking domain knowledge,
Product Management, Development project
management, Application architectural design &
lifecycle management and Process improvement
activities.

Course Outline
3 Wednesday, September 6, 2017
Core Concept
(10 am – 12
pm)
Agile
Manifesto
Agile
Principles
Agile Methods
Scrum
Sprint
User Stories
Estimation
Roles &
Artifacts ( 12
pm – 1pm)
Product Owner
Scrum Master
Development
Team
Activities &
Ceremonies (2
pm – 4 pm )
Backlog
Grooming
Session
Sprint Planning
Daily Scrum
Sprint
Execution
Sprint Review
Retrospective
Agile in TFS (4
pm – 6 pm)
Work Items
Implementatio
ns of work
items
Align with our
existing
practices

Core Concept
4 Wednesday, September 6,
2017

What is Agile
Waterfall
Approach
2017
Agile is a
Set of Values & Principles

Agile Manifesto
Individuals and
Interactions
Process and
ToolsOver
Working
Software
Comprehensive
Documentation
Over
Customer
Collaboration
Contract
Negotiation
Over
Responding to
changes
Following a
Plan
Over
6 Wednesday, September
6, 2017

Agile Principles
2017
Satisfy the customer through early and
continuous delivery of valuable software.
Welcome changing requirements, even
late in development.
Deliver working software frequently
Business people and developers must
work together daily throughout the project.

Agile Principles
2017
 Build projects around motivated individuals.
Face-to-Face communication within a
team.
Working software is the primary measure of
progress.
 The sponsors, developers, and users should be able
to maintain a constant pace.

Agile Principles
2017
 Continuous attention to technical excellence
and good design.
Simplicity--the art of maximizing the amount
of work not done.
 The best architectures, requirements, and designs
emerge from self-organizing teams.
 At regular intervals, the team reflects on
how to become more effective, then tunes
and adjusts its behavior accordingly.

Agile Values
2017
Agile
Values
Trust
Self Growth &
Excellence
Goal Driven
Approach
Sense of
Urgency
High Aims
High
Performance
Accountability

Agile Methods
2017
Popular agile software development frameworks include (but are not limited to)
Adaptive software development (ASD)
Agile modeling
Agile Unified Process (AUP)
Crystal Clear methods
Disciplined agile delivery
Dynamic systems development method (DSDM)
Extreme programming (XP)
Feature-driven development (FDD)
Lean software development
Kanban
Scrum
Scrum ban
Rapid application development (RAD)

SCRUM Framework
2017
 Scrum is not a standardized process. Scrum is a
framework for organizing and managing work.
 The Scrum framework is based on a set of values,
principles and practices.
 Scrum is a refreshingly simple, people-centric framework
based on the values of honesty, openness, courage,
respect, focus, trust, empowerment, and collaboration.
 The Scrum practices themselves are embodied in specific
roles, activities, artifacts, and their associated rules.

SCRUM Framework
2017

SCRUM Practices
Roles
 Product Owner
 Scrum Master
 DevelopmentTeam
Artifacts
 Product Backlog
 Sprint Backlog
 Working Software
Roles
 Sprint Planning
 Daily Scrum
 Sprint Execution
 Sprint Review
 Sprint Retrospective
 Product Backlog
Grooming
Rules
?
2017

Sprints
6, 2017

Time boxing Benefits
6, 2017
Establishes WIP Limit
Forces Prioritization
Demonstrates Progress
Avoid Unnecessary Perfectionism
Motivates Closure
Improve Predictability

Short Duration Benefits
6, 2017
Ease of Planning
Fast Feedback
Bounded Error
Frequent Check Points

Consistent Length
 considering moving from four-week sprint s to two-week sprint s in order
to obtain more frequent feedback but want to try a couple of two-week
sprints before making a final decision.
 The annual holidays or end of the fiscal year make it more practical to run
a three-week sprint than the usual two-week sprint.
 The product release occurs in one week, so a two-week sprint would be
wasteful
6, 2017

No Goal Altering Changes
6, 2017
 An important Scrum rule states that once the sprint goal
has been established and sprint execution has begun,
no change is permitted that can materially affect the
sprint goal.

Definition of Done
 Conceptually the definition of done is a checklist of the
types of work that the team is expected to successfully
complete before it can declare its work to be potentially
shippable.
6, 2017

User Stories
 Template
6, 2017

User Stories
 With Additional Data
6, 2017

User Stories
 With Conditions
6, 2017

User Stories
 Non Functional Requirement
6, 2017

User Stories
 Knowledge Acquiring stories
6, 2017

User Stories
 Story Mapping
6, 2017

User Stories
 Hierarchy
6, 2017

A Good User Story
6, 2017
INVEST
Independent
Negotiable
Valuable
Estimable
Sized appropriately
Testable

Estimation
 What & When We Estimate
6, 2017

Estimation
6, 2017

Planning Poker

Velocity

Burndown

Roles & Artifacts
6, 2017

Product Owner
 Facing two directions simultaneously
6, 2017

Product Owner Responsibilities
6, 2017
Manage Economics
Participate in Planning
Groom the Product Backlog
Define Acceptance Criteria & Verify they are met
Collaborate with the development team
Collaborate with the Stake holders

Product Owner Characteristics
6, 2017
Domain Skill
Is Visionary
Has Business & Domain Expertise
People Skill
Has a Good Relationship
with Stake holders
Is a negotiator
Good Communicator
Powerful Motivator
Decision Making
Empowered to make decisions
Willing to make hard decisions
Takes an Economic Views on
business and Technical Issues
Accountability
Accepts Responsibility for the product
Committed and Available
Acts as a Scrum Team Member

A Day in the life of PO
6, 2017

Who should be a PO
6, 2017

PO Combined with Other Roles
√Same person as product owner for multiple scrum
teams or can be a member of development team.
Same Person as Product Owner and Scrum Master
6, 2017

Scrum Master
6, 2017

Scrum Master Responsibilities
6, 2017
Coach
Servant leader
Interface/Shield
Process Authority
Impediment Remover
Change Agent

Scrum Master Characteristics
6, 2017
Knowledgeable
Questioning
Patient
Collaborative
Protective
Transparent

A Day in the life of SM
6, 2017

SM Combined with Other Roles
√Same person as Scum Master for multiple scrum teams
or must be a member of development team.
Same Person as Product Owner and Scrum Master
6, 2017

Development Team Responsibilities
6, 2017

Development Team Characteristics
6, 2017
Self Organizing
Cross Functional
T Shaped Skill
Collaborative
Right Sized & Long Lived
Focus & Committed
Works @ Sustainable Pace

Development Team
6, 2017

Artifacts
6, 2017
 Product Backlog
 Sprint Backlog
 Working Software

Activities &
Ceremonies
6, 2017

Sprint Planning
6, 2017

Sprint Execution
6, 2017

Sprint Review
6, 2017

Sprint Review Pre work
6, 2017
Determine whom to invite
Schedule the activity
Confirm the sprint work is done
Prepare for the demonstrations
Determine who does what

Sprint Retrospective
6, 2017

6, 2017

Sprint Retrospective Issues
6, 2017
Low Attendance
Ignore the elephant in the room
Poor Facilitator
Blame Game
Complaining Session
Too Ambitious
No follow through

Rules
2017

Implementation
inTFS
2017

6, 2017

Agile project management with scrum

More Related Content

What's hot

Similar to Agile project management with scrum

Recently uploaded

In this document

Agile project management with scrum