Agile Within

The SCRUM way!

1
<< Goal Spectators

Opponents

Team
2
Agenda

Content

Section 1: The Background

Section 2: SCRUM Fundamentals

Section 3: Scrum in Practice

Section 4: Conclusion

3
Global and Growing

The Challenges

Shorter Delivery Cycles/Long Term Customer Commitments

• Customers looking at faster delivery cycles
• Long term customer commitments
• Adaptive solutions to meet customer’s ever changing business environment

More Features/ Better Quality

• Competitive feature game
• Maintain high Production Quality
• Improve Usability

Address New Markets/ Honour Old Customers

• Become present in new Markets and segments
• Deliver as promised
• Improve customer satisfaction & ensure retention

How to go about it!

4
Global and Growing

The Stage

Identify Improvement Areas

• Finding the problem & not the symptom
• Maintain focus on your core competencies
• Work towards the end solution, keep intermediate goals

Start rolling the Ball

• Keep things simple
• Do your analysis before doing anything (Silver Bullet!)
• Get Management Endorsement.

Institutionalize & Adopt Change

• Train and facilitate teams
• Delegate & Empower
• Create Accountability with Responsibility

The SCRUM WAY !

5
Agenda

Content

Section 1: The Background

Section 2: SCRUM Fundamentals

Section 3: Scrum in Practice

Section 4: Conclusion

6
Software Development
Approach

Defined Process Empirical Process

• Processes are well understood and • Input to process is non linear, or too
repeatable complex, non-repeatable
• Predict and Plan • Activities are not predictable
• Change Control to manage “Change” • Control through inspection & adaptation

Waterfall SCRUM !!!

A
Input Discipline

Discipline
Input WORK Output

Discipline
Inspect & Control
Z
Output
7
Understanding SCRUM
What is SCRUM

• Agile Way of Project Management.

Work in your functional team

• Wraps Existing Engineering practices

• A team-based collabrative approach

Scrum Call

• Iteratively & incrementally development

• Always focuses to deliver “Business value”

Collaborative Planning & Review

8
Restart your work again
Understanding SCRUM
SCRUM Roles

Chicken & Pig

9
Understanding SCRUM
SCRUM Roles
SCRUM ROLES
• Product backlog creation, prioritization,.
• Make decisions for customers and users
Product Owner
• Setup and conduct Scrum meetings
• Process guru, Leadership, Coaching..
• Resolves Impediments
Scrum Master
• Self organizing, Cross functional
• Committed & Empowered to do
what is needed to meet Sprint Goal
• To work on Daily Task, update
status of daily task
Scrum Team • Collaboration of Information
COMMITTED
• Management, Customers
• Interested in Project Status
• Funds the Project
Stakeholders INVOLVED
KEY ARTIFACTS
Product Backlog
• List of requirements and Issues
• Owned by a Product Owner
• Anybody can add to it
• Only product Owner prioritizes
Sprint Goal & Backlog
• Goal:
-One sentence summary
-Declared by Product Owner
-Accepted by Team
• Sprint Backlog
• List of tasks to achieve Goal
• Owned by Team, Team modifies
it
Impediments
• List of blocks and unmade decisions
• Owned by ScrumMaster, Updated daily
Increment
• Version of the product/deployable
• Shippable functionality (Tested, 10
documented, etc as per need)
 Understanding SCRUM
SCRUM PROCESS
Sprint Planning
• Hosted by ScrumMaster
(1day)
• IN: (First Half) Product
Backlog, List of requirements
and Issues
• OUT: Select high Priority
items in Product Backlog to
form Sprint Goal
• Team Turns Sprint Goal into
Sprint Backlog
Daily Scrum
• Hosted by ScrumMaster – 15-20
Mins, Same time every day
• Attended by all, stakeholders don’t
speak
• Questions to all team members
•What did you do yesterday>>
•What do you do today >>
•What is in your way >>
• Team Updates Sprint Backlog
• ScrumMaster updates Block list
Sprint Review Meeting
• Hosted by ScrumMaster,
attended by all
• First ½ day: Team Demos
Increments, Reviews Bus
Value
• Rest ½ day: Retrospective,
change if required.
• Announce Next Sprint
Planning Meeting
11
 Understanding SCRUM
Development Process
PRODUCT New Sprint Plan
BACKLOG +Increment
SPRINT New Sprint Plan
SPRINT PLANNING MEETING 30 DAYS SPRINT 2
+Increment
SPRINT
30 DAYS
SPRINT 3
SPRINT SPRINT
SPRINT
GOAL 30 DAYS
GOAL
Daily Scrum SPRINT
Daily Scrum SPRINT
SPRINT GOAL
BACKLOG
BACKLOG
Daily Work Daily Scrum
Daily Work IMPEDIMEN SPRINT
IMPEDIMEN
aily Run Burndown TS BACKLOG
TS
hrough out sprint`` Daily Work
PRODUCT IMPEDIMEN
PRODUCT TS
INCREMENT

Burndown
INCREMENT
SPRINT REVIEW MEETING PRODUCT
INCREMENT
SPRINT REVIEW MEETING

BurdDown
Rate SPRINT REVIEW MEETING
Product backlog

BurdDown
Rate

12
Time
Agenda

Content

Section 1: The Background

Section 2: SCRUM Fundamentals

Section 3: Scrum in Practice

Section 4: Conclusion

13
Scrum in Practice

Pre-Flight Checking

Plan your roadmap

• Identify small yet distinctively measurable goal
• Be clear
• Create internal expertise- Scrum Masters

Do you need a Scrum Tool ?

• Tool is not a necessity, However in large scale projects it facilitates
• It should be team tool, Simple, Fast, Intuitive
• Cost – your decision (From OSS to Many $ per seat)

Prepare your teams

• Get the terminology correct – Train
• Ensure you have all members covered –Seniors as well
• Make them comfortable
• Identify your arbitrators
14
Scrum in Practice
SPRINT 3
SPRINT

Sprint Management
30 DAYS
SPRINT
GOAL

• Sprint Planning (Entry Criteria) Daily Scrum

SPRINT

• Qualitative Goals (Increment) Daily Work

BACKLOG

IMPEDIMEN

• Daily Scrum, Resolving Impediments TS

PRODUCT
• Sprint Reviews and Closures (Exit Criteria) INCREMENT

SPRINT REVIEW MEETING

Meta Scrumming
• For large size projects
• Extending daily Scrums for Program Management
• Create Second level of Scrumming

Managing Releases Sprints Sprints

8
• Release based on Quality
• Release based on Time Box
6
• Release based on Functionality Achieved Backlog
• Or a Combination of all
4
Q-factor
15
2

Time
Scrum in Practice

Challenges

It is a Change Process, Are you ready ;

• Management Support
• Do you have enough Technique/implementation support
• Create a Core Team to work out nitty-gritty
• Are you Empowered to induce change

Discipline…
• Follow the process fully, adopt, refine where you require changes
• If require don’t hesitate from documentation.
• Avoid tendency to go back – midway
• The Roles are Well Identified accepted & respected.
• Daily Scrum is MUST,
-Ensure right audience
-Ensure time boxing
-Ensure clear agenda
16
Scrum Challanges

Things start failing, when

• Team member’s focus moves away from Sprint Goals. Rectify it !
• Stakeholders present/influencing team members participation. Check it !
• Daily Scrum Meetings turns into discussions Stop it!
• Confusion over impediments (Internal/External) Solve it !

Things which are over-sighted

• Increment is demonstrated – But no focus on “Business Value”. Ask what Business Value!
• Stakeholders have other high priority work Stop, Include them !
• Team & Stakeholders say good job, does not measures What done, What left!
• Learning's are NOT moved into Next Sprint Plan Do retrospective check!

17
Agenda

Content

Section 1: The Background

Section 2: SCRUM Fundamentals

Section 3: Scrum in Practice

Section 4: Conclusion

18
SCRUM Benefits

Process Benefit is always difficult to measure (or Claim!)

- Fail>>> Process; Success >>> People
- Be aware and accept it!

Benefits

• Team :
- The teams get focused > One common goal
- Creates self discipline, accountability & responsibility
- Faster, better Communication without barriers

• Stakeholders
• Higher Visibility any time
• Ability to respond and Adapt
• Real software code in early phase of SW life cycle
• Better evaluation, testing, demonstration purposes.

• Organization
• Business Value - ROI
19
SCRUM Benefits

The Road Ahead:

The challenges are to stay

Technology

Business Operations

Agile Within
The SCRUM Way!

20