Implementing Scrum for large scale projects (@DCB14)

Post on 05-Jul-2015

172 views 5 download

Preview:

Click to see full reader

Report this document

description

This presentation is based on a real life experience trying to implement Scrum methodology for one of our large-scale Drupal projects in the Municipality of Copenhagen. I'll be focusing on what our approach is, what challenges the team is facing along the project execution and the lessons learned. Beside all successful stories related to how flexible, how fancy and dev friendly the idealistic Scrum approach is, I will be discussing with you also some of the most critical topics from project management perspective. This is why I’ll put extra focus on how Scrum works in an ideal world and what are the challenges implementing it for a real project: • Why Scrum is good enough to be applied for a complex Drupal project; • Defining and understanding well enough the different roles in Scrum; • “Self-organized team” or how the production team's mindset should be changed; • Is there an option to deliver a Scrum project with already predefined scope and fixed budget; • User stories definition , acceptance criteria, technical debt, retrospective meetings: do we really need to take care of these; • The most common mistakes understanding Scrum and how to prevent them; • Tips that will lead us to a successful project delivery using Scrum;

Transcript of Implementing Scrum for large scale projects (@DCB14)

Implementing Scrum

for large-scale Drupal

projects

#DCB14, November 2014

What this session is aiming for …

• Project Management & Scrum

framework models ...

• Good understanding of the Scrum

approach and its application to a

large scale Drupal project

• PM tips and tricks for success

using Scrum

Software project(s) and Scrum

… or why it is good enough for Drupal projects

Scrum Roles

Product

owner Scrum Master / PM

Dev Team

External stakeholders

Internal stakeholders

The Scrum framework

Master project plan

explore / inspect / adapt

Setting priorities

Incremental delivery

Scrum implementation for the Municipality of

Copenhagen Drupal Multisite project

Project initiation

Functional &

Non-functional requirements

Target System architecture

Performance criteria

Desired delivery date

Initial client requirements:

Budget

The Project Management Triangle

Scope

TimeBudget

Aligning Scrum model together with

the client

Sprints X – Y

Acceptance

(testing & bug-fixing)

Go Live

Support /

Phase 2……………….…

Sprint 0 *

Project kick-off

Communication plan in place

Project level scope – PO vision of the product

desired

Test strategy preparation

Initial discussion about the solution design

Whiteboard preparation

Sprint 0 **

Initial backlog: Epics & User stories definition

Agile doesn’t mean no docs (1)

Master project plan (MS Project)

Agile doesn’t mean no docs (2)

Organizing and maintaining the backlog in Jira

Agile doesn’t mean no docs (3)

User story definition in Jira: from the epics to the bugs

Agile doesn’t mean no docs (4)

Organizing test cases in Test Link

Agile doesn’t mean no docs (5)

Product backlog

Release burn-down chart

Sprint burn-down chart

… in a simple XLS - showing some examples

Project tracking (1)

Project tracking (1)

Agile doesn’t mean no docs (6)

Continuous releases & Automated tests (based on

Mink & Behat)

Thank you!

Q&A

Copyright © 2022 FDOCUMENTS