Succeeding with SCRUM

Sharique Khan

Everyone goes home on time…by .. Cutting the confusion Cutting Waste (feature creep) Better Visibility Surfacing the risks and challenges early Protecting the team Delivering software we are proud of Happy Customers & more business

You don't need any documentation

Agile means no plan

Agile doesn't need up front architecture & design

No managers / leads thank you, we are doing Scrum!

You need only three roles: PO, SM and team

One can learn Agile from a book

Dilution of Responsibility & Accountability

Establish Product Vision

Re Visit Roles / Responsibilities / Accountability

Staffing & Resource Planning

Trainings – Technology , Scrum

Architecture & Design

Risk Identification – Technology , Skill, People

Everyone needs to understand Why are we doing this?

How this is going to do cost saving or generate more profit?

How this product will be better than competition?

What problems this product solves?

User stories at times do not reflect the exact requirement… so for each story we should know : Functionality Ux Performance Security ……

Installer in every sprint

Integration in every sprint

System Testing in every sprint

People Product Owner – only 1 Scrum Master – only 1 Team – (size < 7, co located, motivated)

SCRUM Framework Sprint Planning Sprint Review Sprint Retrospective Product Backlog Grooming Daily Stand Up

Artifacts Release Backlog Product Backlog Sprint Backlog Sprint Burn down

Scrum Master & Tech lead / Architect should be actively working to remove and obstacles

Lack of Solid Design is not SCRUM

Also too much detailed design upfront is also not SCRUM.

In Sprint-Zero good architecture & design which is scalable should be established.

It is a list of Prioritized & estimated User Stories and ..

Outstanding defects

Skilled

Passionate

Willing

Preparation for the next sprint Identify & Mitigate Risks for next sprint stories Establish design enhancements for next sprint Establish Test Strategy for next sprint

That’s all folks !!..