Cornel Fatulescu - Envisaged Collaboration Framework - CodeCamp 25 oct 2014

AGILE ADOPTIONfrom the trenches

Cornel FATULESCU

agile coach

Product Backlog

Chief Product Owner

Sprint Planning2 hours

Sprint2 weeks

Sprint Review2 hours

Sprint Retrospective

1.5 hours

Product Team

SprintBacklog

Product Team Product

Team

Refinement

Definition of Ready

Case study

• Big International Group >10k employees• Top management changed several times in 2

years• Building their IT Solution for 61 countries• Already a team in place of more than 10

people• Willing to work in Scrum• Project started for 2 years and nothing was

released

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

It is always about change

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Leading change

1. Sense of Urgency2. Guiding coalition3. Vision & Strategy4. Communicate the change vision5. Empower Broad-Based Action6. Generate short-term wins7. Consolidate Gains & Make more change8. Anchor new approaches in the culture

John Cotter

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Preparations

• I’ve been an observer at 2 events• Meeting – something regarding the

Enterprise Architecture• Sprint Review, Retrospective, Planning

• Made a proposal for a SMART step

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Preparations

• As an Agile Consultant, I will help the Business Team to better prepare the next Sprint Planning, so that the team will focus on activities the event was really meant for.

• Deadline: before the next sprint planning• Budget: 5 days

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Acceptance criteria: Very good

Given the next Sprint Planning,When the length of the 1st topic “What can be done during the sprint?” <1hand ROTI>2and PM and MD will evaluate the effects of the consulting missionThen the result is “Very good!” and the client will pay the rest of 60% of the order.

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Acceptance criteria: Good

Given the next Sprint Planning,When the length of the 1st topic “What can be done during the sprint?” is between 1h and 2hand ROTI>2and PM and MD will evaluate the effects of the consulting missionThen the result is “Good!” and and the client will pay the rest of 60% of the order.

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Acceptance criteria: Mission failure

Given the next Sprint Planning,When the length of the 1st topic “What can be done during the sprint?” >=2hand PM and MD will evaluate the effects of the consulting missionThen the result is “Not good!” and the client will not have to pay the rest of 60% of the order.

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Leading change


John Cotter

First Step

• I’ve listened• Small and quick improvements• Mediated events & conflict management• Passed the 1st evaluation (Mission

finished)

Business Team

Developers

SprintBacklog

Sprint Planning

3.5 hours

Sprint2 weeks



0.5 hours

DevelopersDefinition of Done

Business Lead

What I found?Managing Director

(hierarchically responsible)

Program Manager(budget

responsible)

Software Architect

Enterprise Architect

Managing Director(More

technical)

2 Product Owners

1 Business Analyst

PruductBacklog

Fired Scrum Master

It started like...

Leading change

Vizualize Smell Change

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Leading change


Second step

• Communicate the change vision• Conflict management• Continued helpping the business team• Started to work a little with

development team• Establish the collaboration framework

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Development Team

Product Team

SprintBacklog

SprintBacklog

Increment


Sprint2 weeks



1.5 hours

Developers

Business Team(Area

Product Owners)

Business Team

Business Team

Business Team

Developers

Refinement

Refinement

Definition of Done

Definition of Ready

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog

Business Team

Refinement

Definition of Ready

Business Team(Area

Product Owners)

Product Backlog

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Definition of Ready

Functionality has the following attributes:• Summary• Description in User Story format• Acceptance criteria• Associated screens• Testing Data when needed

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Business team: Product Suggestions flow

Chief Product Owner

List of Suggestions(or Large User Stories)

TODOIn

ProgressPeer

ReviewReady for inspection during Sprint Review

Area Product Owners

Chief Product Owner


Sprint2 weeks



1.5 hours

Development Team

Product Team

SprintBacklog

SprintBacklog

Increment


Sprint2 weeks



1.5 hours

DevelopersBusiness Team

Business Team

Business Team

Developers

Refinement

Refinement

Definition of Done

Definition of Ready

Business Team(Area

Product Owners)

Product Backlog

Chief Product Owner

Development Team

SprintBacklog

Increment


Sprint2 weeks



1.5 hours

DevelopersBusiness Team

Business Team

Developers

Refinement

Definition of Done

Product Backlog

Product Backlog

Chief Product Owner

Development Team

SprintBacklog

Increment


Sprint2 weeks



1.5 hours

DevelopersProduct Team

Product Team

Developers

Refinement

Definition of Done

Definition of Done for a User Story

Each functionality is considered Done when:• All development tasks are done

• All code is checked-in• All unit tests are checked-in• All unit tests pass• All code and test code is reviewed (Peer review)

• All Jenkins jobs pass• All acceptance criteria pass• All functional tests are:

• Executed & pass

• Something missing?

Product Backlog

Chief Product Owner

Development Team

SprintBacklog

Increment


Sprint2 weeks



1.5 hours

DevelopersProduct Team

Product Team

Developers

Refinement

Definition of Done

Definition of Done for a Sprint

Each sprint is considered Done when:• All stories and their associated tasks are done(The Sprint has a goal. During the Sprint Planning the Product Owner should indicate which stories are critical in order to achieve that Goal and consider the Sprint Accepted or Refused)• All orphan tasks are done:

• manual deploy, • End-to-end test cases,• non-functional tests pass, • etc.

• Code coverage is at least 80%

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Development Team: User Stories flow

Area Product Owners

List of User Stories Considered Ready

TODOWork In Progress

APO Feedback

Done

Development team

Increment

Chief Product Owner Area 1

Product Backlog

Area 2 Product Backlog

Area 3 Product Backlog

In the future?

Joint Retrospective

1.5 hours

Development Team 1

(Feature Team )

Scrum Master

Development Team 2

(Feature Team )

Development Team 3

(Feature Team )

Area 1 Product Owner



Product Backlog

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

And there is more...

Area Product Owners

To be accepted

IntegrationTesting

...Ready to Release

Development team

...

In Acceptance

Software tools VS simple tools

CPO got fired!Business team was

confused

Product Backlog

Chief Product Owner


Sprint2 weeks



1.5 hours

Product Team

SprintBacklog


Team

Refinement

Definition of Ready

Leading change


Third step

• Step out of the project• Give the lead to another Pentalog

Institute coach specialized in building strong teams

• Make regular reviews (ones or twice per month)

Questions & Answers

Cornel Fatulescu - Envisaged Collaboration Framework - CodeCamp 25 oct 2014

Software

Transcript of Cornel Fatulescu - Envisaged Collaboration Framework - CodeCamp 25 oct 2014