• Like
  • Save
Advanced topics in Agile: Implementing Scrum in a project-based company
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Advanced topics in Agile: Implementing Scrum in a project-based company

  • 564 views
Published

A lecture I gave in the Agile Saturday event - Sept 28 2013 …

A lecture I gave in the Agile Saturday event - Sept 28 2013

Some of the main Scrum goals are to be able to prioritize often and have less paperwork done. This contradicts with project-based software development where project scope and deadlines are predefined and signed-off by the customer. This session presents how Videobet has implemented Scrum in such an environment.

--Agenda--
Agile Enterprise Patterns
Project definition and how it collides with Scrum/Agile values
The role of the Product Owner in a project-based environment
The role of the Scrum Master in a project-based environment
Scrum of Scrums!? Multiple concurrent projects management
User stories, point estimation and velocity charts – are they relevant at all?
In-sprint testers role vs. QA role
Tools and infrastructure to support Agile transformation
Q&A

Published in Technology , Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
564
On SlideShare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Expand project mode in VB slide; expand on Playtech
  • talk about multi-functional a bit more
  • Focus a bit more on multi-project aspects

Transcript

  • 1. Scrum in a Project-Based Company Advanced Topics in Agile Ethan Ram / 28 Sep 2013 V0.9 © All rights reserved Want to use slides from this presentation? Ask for permission: ethanram@gmail.com
  • 2. Ethan Ram - Bio • Chief architect of Videobet • Leading Videobet’s R&D and OPs teams Agile Injection effort • As VP R&D of GameGround transformed the R&D to run in Kanban in a Continuous Deployment environment • Hacker in soul and a Windows Internals hobbyist Find me here: •ethnram@gmail.com •LinkedIn •The Null Terminator blog 10/03/13 © All rights reserved 2
  • 3. Videobet • A Playtech division • Innovative Gaming Platform Provider – Established 9 years ago – 150 employees in Tallinn and Kiev – Operate in 9 countries – 60% of UK market • R&D – Front-end teams (C++) – Server teams (Java) – Game development teams 10/03/13 © All rights reserved 3
  • 4. Agenda • Agile and the project development manifesto • How Videobet adapted Scrum • Multi-project - Scrum of Scrums • User stories, velocity for estimations? • Real-life examples • Q&A “Not all Scrums Are Born The Same” 10/03/13 © All rights reserved 4
  • 5. The Agile Project Manifesto Agile Manifesto (bytes) • Early and continuous delivery of valuable software • Welcome changing requirements, even late in development • Deliver working software frequently • Continuous attention to technical excellence My Manager’s Manifesto 10/03/13 • Signoff business requirements • Signoff solution document and schedule • Change Requests open scope • Customer is far away • Deliver once at the end of the project • Technical excellence is nice to have – delivering on time is must have! © All rights reserved 5
  • 6. Patterns of Enterprise Agility 10/03/13 Business Context Delivery Pattern Delivery Lifecycle Upfront requirements and design; develop; signoff Old-school (Hardware, Banking software, Mil-spec) Web-based product development (mobile apps, social apps…) Product tailored to a specific customer (ecommerce, retail, gaming) © All rights reserved 6
  • 7. The Scrum Team 10/03/13 © All rights reserved 7
  • 8. The Road to the Backlog •Need time to analyze edge cases •Integration is the hardest part •It’s easy to break product integrity >> senior mgr. signoff plans •Managers committing to timeline need good estimations •User Stories are sub-optimal for infra. work, backwards- compatibility, refactoring etc. 10/03/13 © All rights reserved 8
  • 9. The Product Owner Role Vanilla Scrum • Define the features of the product • Decide on release date and content • Responsible for the profitability of the product (ROI) • Prioritize features according to market value • Accept or reject work results • Adjust features and priority every iteration, as needed VB Scrum • Represents the customer view to the team • Responsible for integrity and completeness of solution • Analyze feature details and writes SRS document • Guide tester in writing the test plan • Work closely with the devs to make sure they get it right • Adjust features and priorities every iteration, as needed 10/03/13 © All rights reserved 9
  • 10. Multi-Project Aspects One project • Project timeline • Scrum team backlog Many projects • Multiple committed timelines • Multiple Scrum teams • Multiple team backlogs • Large projects requiring a few teams • Roadmap backlog 10/03/13 © All rights reserved 10 !?!?!?
  • 11. Scaling Up: Scrum of Scrums • “Scalability comes from teams of teams” • “Scrum has been used on multiple 500+ person projects” 10/03/13 © All rights reserved 11
  • 12. Multiple Teams in a Scrum Project 10/03/13 Epic 1 Epic 2 Epic 4 GoldW1 W2 W3 W4 W5 W6 W7 W8 W9 Planning Review Prepare Project Backlog Sprint Backlog buildup (SRS) Initiate Sprint Prepare Sprint Backlog Sprint Backlog buildup (SRS) Initiate Sprint Prepare Sprint Backlog Sprint Backlog buildup (SRS) Initiate Sprint Prepare for next project Backlog Kick-off Epic 1 Epic 5 Epic 2 Epic 5 Epic 3 Epic 2 Stabilize Stabilize Stabilize Retrospective Feature Freeze © All rights reserved 12
  • 13. Company Backlog to Team Backlog Input •Field issues >> bugs •Project >> 1-10 Epics •Roadmap >> 1-5 Epics •Internal >> Epic Tips •One Epic / project - one team •Group bugs to an Epic •Plan ahead 2-3 sprints to enable “backlog grooming” – Research solutions – Learn product and code – Raise open issues – Allow Product Owner to be prepared •Have several internal Epics ready in Product Backlog 10/03/13 © All rights reserved 13 Epic Epic Epic Sprint 1 Sprint 2 Backlog Sprint 1 (Spike) Sprint 2 Backlog (Spike) Sprint 1 Sprint 2 Backlog
  • 14. Project Effort in Sprints 10/03/13 sprint Amount of hours 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Sprints Stabilize BugsPrepare Backlog Initiate Sprint © All rights reserved 14
  • 15. Elephants Mapping To Sprints 10/03/13 sprint 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 © All rights reserved 15
  • 16. Real-Life Projects Mapping To Sprints Jun 24Jun 24thth -Jul-Jul 55thth Jul 8Jul 8thth -19-19rdrd Jul 22Jul 22ndnd -Aug 2-Aug 2ndnd • 30% v1.1 defects • 40% SAL 5.02 • 30% Field Issues • 20% v1.1 defects • 40% SAL 5.02 • 30% Field Issues • 10% Product BL • 10% v1.1 defects • 40% SAL 5.02 • 20% Field Issues • 10% Product BL Aug 5Aug 5thth – 19– 19thth • 10% v1.1 defects • 40% SAL 5.02 • 10% Field Issues • 40% Product BL Jun 24Jun 24thth -Jul-Jul 55thth Jul 8Jul 8thth -19-19rdrd Jul 22Jul 22ndnd -Aug 2-Aug 2ndnd • 60% v1.1 defects • 20% LB-V2 • 20% Field Issues • 5% Game engine • 30% v1.1 defects • 30% Field Issues 40% Game engine • 0% v1.3 • 10% v1.1 defects • 20% Field Issues 30% Game engine • 10% v1.3 Aug 5Aug 5thth – 19– 19thth • 10% v1.1 defects • 10% Field Issues • 30% Game engine • 20% v1.3 Jun 24Jun 24thth -Jul-Jul 55thth Jul 8Jul 8thth -19-19rdrd Jul 22Jul 22ndnd -Aug 2-Aug 2ndnd • 10% v1.1 defects • 20% LB-V2 • 60% Fortune Game • 10% Field Issues • 10% v1.1 defects • 50% Fortune Game • 10% Ghosts Game • 30% LB-V2 • 10% Field Issues • 10% v1.1 defects • 20% Fortune Game • 40% Ghosts Game • 10% Field Issues 2 Vacations (Rain, Nastya) >> 80% Aug 5Aug 5thth – 19– 19thth • 10% Fortune Game • 30% Ghosts Game • 10% Field Issues • 10% Product BL 3 Vacations (Rain, Nastya, Andre) >> 60% Current Sprint10/03/13 © All rights reserved 16
  • 17. The Scrum Master • Represents management to the project • Responsible for enacting Scrum values and practices • Removes impediments • Ensure that the team is fully functional and productive • Enable close cooperation across all roles and functions • Shield the team from external interferences (“Dark forces”) • Does NOT allocate tasks << all of that and… •Make sure the allocation of resources to projects is maintained 10/03/13 Vanilla Scrum VB Scrum © All rights reserved 17
  • 18. Quality Assurance in VB Scrum Dev Testers Role • Part of the Scrum team – Assist in achieving sprint goals • Create test and integration environments for the team – Work on team branch snapshots • Update regression tests for QA • Work with devs to verify that features work correctly – Dev-requests – Defects – from Sprint or QA • Create/update automated integration tests QA Testers Role • Gets a build “after” sprint is over – Formal release build • Customer-like environment • Verify overall product quality – Build sanity – Full regression test plan • Focus on “touched” features – Use build notes to build a relevant test plan • Load/stress testing • Report on reproducible defects • Sign-off release 10/03/13 © All rights reserved 18
  • 19. Multi-Project View from JIRA 10/03/13 © All rights reserved 19
  • 20. Multi-Project View from JIRA 10/03/13 xxx aBC aBsddlfhasldjhlshC © All rights reserved 20
  • 21. Multi-Project View from JIRA 10/03/13 xxx aBC aBsddlfhasldjhlshC © All rights reserved 21
  • 22. Velocity for Planning? 10/03/13 © All rights reserved 22
  • 23. Agile Tools Seminar Invitation! • Session presents the automation model developed in Videobet, the tools used in the R&D, QA and operations: – Greenhopper; Flyway DB; Maven & Nexus; QuickBuild; Sonar; Selenium Grid; Test Rail, Socorro and more… • Open discussion • Refreshments & tour in Videobet office 10/03/13 © All rights reserved 23 Videobet, Paldiski Mnt. 29, TallinnVideobet, Paldiski Mnt. 29, Tallinn Register in the Videobet booth – Win an iPad MiniRegister in the Videobet booth – Win an iPad Mini Wednesday, 16 Oct ‘13 @ 16:30-19:00Wednesday, 16 Oct ‘13 @ 16:30-19:00
  • 24. Q&A Mountain Goat Software, LLC Presentation based on 10/03/13 © All rights reserved 24 Thanks!