Implementation Scrum in Organization Level

Welcome
to
Monthly Agile Bangladesh Meet up
5/29/2017Copyright © Zahid Hasan, CSM®,CSPO® 1

5/29/2017 Copyright © Zahid Hasan, CSM®,CSPO® 2
Implementation SCRUM
in
Organization Level
Conducted By
Zahid Hasan, CSM®, CSPO®
Senior Systems Analyst, Synesis IT Limited

Some of my Certifications:
• SCRUM Fundamental Certification (SFC)
• Certified SCRUM Master (CSM®)
• Certified SCRUM Product Owner (CSPO®)
• Six Sigma Yellow Belt
• Agile Project Management
• Agile at Work: Building Agile Team
• Agile at Work: Planning with Agile User Story
• Cyber Security
• Security Awareness for IT Professional
• Security Awareness for Managers

What is Agile
Agile is an iterative approach to planning and guiding project
process by using a self organizing collaborative team.
5/29/2017 Copyright © Zahid Hasan, CSM® 4

The Agile Manifesto
 Individuals and interactions over processes and tools
 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan

The Agile Principles
• [Satisfy the customer] through early and continuous delivery of
valuable software.
• [Welcome changing requirements] even late in development.
• [Deliver working software frequently] from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
• [Business people and developers must work together] daily
throughout the project.
• Build projects around [motivated individuals]. Give environment
and support they need, and trust them to get the job done.
• [Working Software] as primary measure of progress.

The Agile Principles - continued
• The sponsors, developers and users should be able to [maintain a
constant pace].
• [Continuous attention] to technical excellence and good
design enhances agility.
• [Simplicity] — the art of maximizing the amount of work not done.
• At regular intervals, [the team reflects on how to become more
effective] and adjust its behavior accordingly.
• The best architectures, requirements, and designs emerge
from[self-organizing teams].
• [Face to face communication] with and within team.

Agile Values
Agile
Values
Trust
Accountabil
ity
High
Performanc
e
High Aim
Sense of
Urgency
Goal Driven
Approach
Self Growth
and
Excellence

Agile Frameworks
Scrum XP
Battlefield
Agility
Kanban
DAD
Agile
Modeling
Agile
Modeling
Krystal
DSDM SAFe Nexus Less

What is Scrum?
 Scrum is an interactive and incremental Agile software
development framework for completing projects.
 Scrum originally was formalized for software development
projects, but it works well for any complex, innovative scope
of work.
 The Scrum framework is deceptively simple.
 Scrum is time focused.

Some famous users of SCRUM

Scrum Main Principles
 Small “Shippable” increment of development
 High quality working software ……. Continuously
 On-going integration during development
 Cross-Functional team
 Self Managed
 A Shared Journey with Customers

Scrum Values
Focus
Openness
CourageCommitment
Respect

Scrum Disadvantages
 Makes all dysfunction visible
 Scrum doesn’t fix anything: the team has to do it
 Feels like things are worse at the beginning
 Some teams and organizations are not right or ready for it
 Team willingness, capabilities
 Management buy-in
 Risk of turnover during adoption
 Some people will refuse to stay on a Scrum team
 Some people will refuse to stay if Scrum is abandoned
 Partial adoption may be worse than none at all
 If adoption fails, time will have been wasted, and some
people may leave

Scrum Skeleton
• Collaborative and Self
Managed.
• Customer engagement
• Represent work or value
• Transparency and
Opportunity
• Time box event
• Every event has a
maximum duration
• Product Owner
• Development Team
• SCRUM Master
Roles
• Sprint – 1w – 4w
• Sprint Planning – 1h@1w
• Daily Standup – Max 15min
• Sprint Review – 1h@1w
• Sprint Retrospective – 45m@1w
Event/
Ceremony
• Product Backlog
• Sprint Backlog
• Burn down chart
• Visual Task board
Artifacts

The Scrum

The Scrum Team
Product Owner
• Define Product
Vision
• Responsible for
ROI
• Manage the
Product Backlog
• Approve ‘Done’
Development
Team
• 6, + or – 3
• Cross-functional
• Self-managing
Scrum Master
• Safeguards the
process
• Protects team
• Ensures visibility
of team’s progress
• Removing barriers
between
development and
product tem

Product Owner
 Responsible for the overall project vision and goals
 Responsible for managing project ROI vs. risk
 Responsible for taking all inputs into what the team should
produce, and turning it into a prioritized list (the Product
Backlog)
 Participates actively in Sprint Planning and Sprint Review
meetings, and is available to team throughout the Sprint
 Determines release plan and communicates it to upper
management and the customer

Development Team
 6 people, + or – 3
 Can be shared with other teams (but better when not)
 Can change between Sprints (but better when they don’t)
 Can be distributed (but better when colocated)
 Cross-functional
 Possesses all the skills necessary to produce an increment of
potentially shippable product
 Team takes on tasks based on skills, not just official role.
 Self-managing
 Team manages itself to achieve the Sprint commitment

Scrum Master
A ‘Servant Leader’
Who:
• Safeguards the process, not the project. Making sure team lives by
the values and practices of Scrum
• Facilitates Scrum Process
• Facilitates creativity and empowerment
• Helps in improving the productivity of the scrum team in any way
possible
• Facilitates team self organization, keeping them in the zone.
• Protects the team so they can focus on meeting their commitments
with high availability.
• Removing the barriers between development and product tem (PO)
• Ensures full visibility of team’s progress.

Adopting SCRUM in any organization

Call a meting on next working day
Asked the team to follow SCRUM

SCRUM Implementation
Educate your Management on SCRUM
Provide a clear idea of SCRUM to
your customer
Collaborate with team
Start Journey with SCRUM

SCRUM Education for Management
Explain the principles of SCRUM
Explain SCRUM values, focus on
commitment, focus, and courage
Explain about SCRUM artifacts, specially
Sprint Backlog & Burn down Chart
Explain about SCRUM events, specially
Daily Standup, Sprint Retrospective

Impact of SCRUM educated management
Thinking about SCRUM
Start to learn SCRUM
Dream to start SCRUM

Provide a clear idea to customer
Explain the principles of SCRUM, mainly
Shippable delivery and High Quality
software
Explain about SCRUM artifacts, specially
Product Backlog, Burn down Chart &
Visual Task Board
Explain about SCRUM events, specially
Sprint Review, Sprint Retrospective

Impact of Customer Idea
Thinking about SCRUM
Internet surfing for SCRUM
Talk with other people
Talk with your management

Team Collaboration
Discuss about SCRUM values
Explain about self managing team structure
Explain about SCRUM master role who will work for
their protection and benefits
Explain about artifacts like sprint backlog, task board
Talk about scrum ceremony mainly Sprint Planning
meeting with estimation, and daily standup meeting

Impact of team collaboration
Immediately start SCRUM learning
Try to follow SCRUM ceremony and artifacts
Start practicing SCRUM
Eager to be a SCRUM team member
Try to convince immediate supervisor to shift on SCRUM

Okay…. Organization is agreed to follow SCRUM
What is the next Steps?

Arrange a workshop about Scrum.
Below listed topics should be covered:
• SCRUM Principle
• SCRUM Values
• SCRUM Team & their responsibilities
• SCRUM Events
• SCRUM Artifacts
• Story Definition
• Task Estimation
• SCRUM Metrics

• Select a new or existing small/medium project
to startProject
• Plan a two weeks sprint
• Take lees work
SPRINT
• Build team with 3 to 9 person.
• Please don’t try to start with multiple teams
• Select SCRUM Master
SCRUM Team
• Start with Sprint Back log
• Place a scrum board
Artifact Selection
• Daily Standup meeting
• Print Retrospective
SCRUM Ceremony
SCRUM Journey…….1st SPRINT

• Plan another two weeks sprintSPRINT
• Select Product OwnerSCRUM Team
• Introduce Product Back log
• Establish a Burn down Chart
Artifact Selection
• Introduce Sprint Review MeetingSCRUM Ceremony
SCRUM Journey….2nd SPRINT

• Plan another two weeks sprints
• SCRUM Master will ensure that SCRUM is
properly following this project
Sprint
• More familiar with SCRUM
• Practicing SCRUM more
SCRUM Team
• Using every artifacts of ScrumArtifact
• Introduce Sprint Planning MeetingSCRUM Ceremony
SCRUM Journey….3rd SPRINT

SCRUM Journey….4th SPRINT
Yes…. You are now a SCRUM Practitioner;

Implementation Scrum in Organization Level

More Related Content

What's hot

Similar to Implementation Scrum in Organization Level

Recently uploaded

Implementation Scrum in Organization Level