agile@barclays - elearning.esi-intl.comelearning.esi-intl.com/blendedlearning/ilt/gmv001... ·...

Agile@Barclays

participant guide

www.esi-intl.co.uk

AgilePractitioner

gmv-in.ppt

Welcome

Some “housekeeping” items… • Fire procedure• Emergency phone number• Facility layout

Introduction

© ESI April 2015 IN-1

gmv-in.ppt

Course Overview

• Introduction• Module 1: The Agile Manifesto and Principles• Module 2: What does Agile mean to Barclays?• Module 3: Setting Up for Agile Delivery• Module 4: Agile Delivery• Module 5: Agile Transition• Module 6: Next Steps• Module 7: Course Closeout


Introduction

gmv-in.ppt

Learning Objectives

• Identify and use Agile terminology• Explain the transition from waterfall to Agile at Barclays• Apply the Barclays Agile framework into your own

projects• Demonstrate Agile ceremonies and practices through

practical exercises


Introduction

gmv-in.ppt

Team Introductions

• In teams, prepare a short introduction to each teammember

• Any format you like• Presentations to other groups• No more than 5 minutes for each presentation!• Preparation time = 10 minutes


Introduction

gmv-01.ppt

Agile Manifesto

• We are uncovering better ways of developing software by doing itand helping others do it. Through this work we have come to value:

Process and Tools

Comprehensive Documentation

Contract Negotiation

Following a Plan

Individuals and Interactions over

Working Product over

Customer Collaboration over

Responding to Change over

1-1 © ESI April 2015

Module 1

gmv-01.ppt

Agile Principles 1

• Our highest priority is to satisfy the customer through earlyand continuous delivery of valuable product

• Welcome changing requirements, even late in development.Agile processes harness change for the customer'scompetitive advantage

• Deliver working product frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale

• Business people and developers must work together dailythroughout the project

• Build projects around motivated individuals. Give them theenvironment and support they need, and trust them to get thejob done

• The most efficient and effective method of conveyinginformation to and within a development team is face-to-faceconversation

© ESI April 2015 1-2

Module 1

gmv-01.ppt

Agile Principles 2

• Working product is the primary measure of progress• Agile processes promote sustainable development• The sponsors, developers, and users should be able to

maintain a constant pace indefinitely• Continuous attention to technical excellence and good

design enhances agility• Simplicity─the art of maximizing the amount of work not

done─is essential• The best architectures, requirements, and designs emerge

from self-organizing teams• At regular intervals, the team reflects on how to become more

effective, then tunes and adjusts its behaviour accordingly


Module 1

gmv-02.ppt

Agile is a “State of Mind”

• Structured Project Management methods and BoKs arefocused on management, governance and control

• Agile frameworks are focused on Users and those whocreate products and solutions

• The Barclays implementation of Agile will be part of a“bigger picture”

• “Our Way Of Working” (– formerly DDLA)

Module 2


gmv-02.ppt

Our Way of Working

Module 2


gmv-02.ppt

Overview of BACL

• The Barclays Agile Change Lifecycle (BACL) is built fromthe events it contains

• The BACL brings control to the Agile way of workingwithout losing the benefits

Module 2


gmv-02.ppt

Barclays Agile Change Lifecycle

Module 2


Module 3

gmv-03.ppt



Module 3

gmv-03.ppt

Inception

• Also known as “Iteration Zero” when performed at thestart of the project

• An opportunity to lay the foundations for successfulConstruction and Transition

• Iterative – also checked and updated at the start of eachIteration


Module 3

gmv-03.ppt

The Product Vision and “Bus Stops”

• A high level description of the intended delivery from thiswork

• Gets buy-in from stakeholders• Ensure commonality of vision for business, entire team

and stakeholder groups• Provides direction through lifecycle• May vary over the life of the work• In Barclays we have “Bus Stop” visuals


Module 3

gmv-03.ppt

Bus Stop Visuals

• A method for quicklyillustrating thestrategic direction ofthe work we willundertake

• Gets buy-in from alllevels

• Should be fun toproduce


Module 3

gmv-03.ppt

A Challenge For You…

• The challenge for today:– New mobile phone app

• You will be working with this idea through the day• We will demonstrate the power of Agile management

through practising the ideas and techniques we learnabout!


Module 3

gmv-03.ppt

Bus Stop Exercise

• As a team, decide on a newmobile app

• Working in your team, createa Bus Stop visual

• This should be createdquickly, and offer enoughincentive for a senior teammember to decide whetherto proceed with your idea…

• Development timebox: 20minutes

• Presentation timebox: 5minutes per team


Module 3

gmv-03.ppt



Module 3

gmv-03.ppt

Agile Requirements

• No over-arching detailed requirements specificationagreed at start

• Start with high-level description of the requirements anddevelop detail iteratively as work progresses

• User feedback vital for a successful solution• May use Epics and User Stories


Module 3

gmv-03.ppt

Epics and User Stories

• Epics and User Stories are constructed in the sameframeworkAs a <type of user>, I want <some goal>, so that <some reason>

• A way of ensuring that the development aims are in linewith user requirements

• Solution agnostic• Permit the team to use efficient and creative approaches

to deliver required functionality


Module 3

gmv-03.ppt

Barclays User Story Example

© ESI April 2015 3-10

Module 3

gmv-03.ppt

Epics Become User Stories…

• Put simply, Epics are large User Stories• Epics are Stories that can’t be delivered in a single

iteration• Epics can be categorised

– Compound (many independent stories within one)– Complex (many linked stories within one)

• Epics must be broken down into stories before they canbe delivered

• Most User Stories are derived from Epics

© ESI April 2015 3-11

Module 3

gmv-03.ppt

INVEST in your Stories

• Independent• Negotiable• Verifiable• Estimable• Small• Testable

© ESI April 2015 3-12

Module 3

gmv-03.ppt

Estimating User Stories and Epics

• We need a technique which allows fast estimation of UserStories

• Can use “Story Points” (size based)• Or can use “Complexity Points” (difficulty based)• Continuous scales are slower, stepped scales are less flexible• Modified Delphi Techniques are often used

– Planning Poker– T-Shirt Sizing– Jelly Beans, etc.

© ESI April 2015 3-13

Smallest Small Medium Med-large Large Epic

Module 3

gmv-03.ppt

Modified Delphi Estimation

• Modified Fibonacci Series• Fast and efficient estimating method• Collaborative – whole team• “Better to be vaguely right than exactly wrong” – Carveth

Read• Smaller or less complex stories have fine scale• Larger or more complex stories have rough scale• Easy way to separate User Stories from Epics• Smaller stories are more “ready” for development

© ESI April 2015 3-14

Module 3

gmv-03.ppt

Product and Iteration Backlogs

• Epics and User Stories areplaced in a list called the“Product Backlog”

• One Product Backlog per Agileteam

• Product Owner “owns” theProduct Backlog

• Team selects items from theProduct Backlog and creates an“Iteration Backlog” for eachIteration

• Team aims to complete theIteration Backlog during theIteration

© ESI April 2015 3-15

Module 3

gmv-03.ppt

Product Backlog Prioritisation

• Product Backlog prioritised by Product Owner in collaborationwith team and stakeholders as required

• Priority order is used at Barclays, for example 1 to 100• Prioritisation may be in terms of

– Business Value– Point value– Risk– “Low hanging fruit”– Marketing / PR– First mover advantage– Any mix of the above

• May use “Pairwise Comparison” Technique

© ESI April 2015 3-16

Module 3

gmv-03.ppt

Product Backlog Exercise

• In your teams, generate the initial Epics and User Stories (asyou are able) for your app

• Use “Post-It” notes to record your items• Get the functionality described at a high level• May well be mainly Epics at this early time• Prioritise the Product Backlog and be prepared to justify your

prioritisation• Preparation time: 20 mins

© ESI April 2015 3-17

Module 3

gmv-03.ppt

Estimation Exercise

• In your teams, estimatethe initial Epics and UserStories for your app

• Add estimates to your“Post-It” notes

• Preparation time: 10 mins• Presentation time: 5 mins

per team

© ESI April 2015 3-18

Module 3

gmv-03.ppt


© ESI April 2015 3-19

Module 3

gmv-03.ppt

Release Planning

• The “Release Plan” describes at a high level– The functionality (Epics / User Stories / Items) that will

be delivered– When this functionality will be delivered

• Allows the business to prepare for– Beneficial Use– Resourcing the delivery and user teams– Marketing / rollout– Minimum Valuable Product delivery

• Based on the Product Backlog

© ESI April 2015 3-20

Module 3

gmv-03.ppt

Velocity

• Velocity is the capacity of the team to deliver Story Pointor Complexity Point value during each iteration

• Decide on Iteration Duration and estimate ability to satisfyProduct Backlog items

• Iteration Duration should be consistent throughout work(after Iteration Zero)

• Likely to be arbitrary estimate early in Lifecycle, rollingthree-point estimate later on

• Velocity should increase as team maturity increases

© ESI April 2015 3-21

Module 3

gmv-03.ppt

Sample Release Plan Structure

Iteration 1

Iteration 2

Iteration 3

Iteration 4

Iteration 5

Iteration 6

Iteration 7

© ESI April 2015 3-22

Module 3

gmv-03.ppt

Release Plan Exercise

• In your teams, create the Release Plan for your app• Your Release Plan will describe when functionality will be

delivered to users• Be prepared to justify your “Functionality Drop” timings• Remember that you will need to estimate Velocity and

factor-in proposed Iteration Duration• Preparation time: 15 mins• Presentation time: 5 mins per team

© ESI April 2015 3-23

Module 3

gmv-03.ppt


© ESI April 2015 3-24

Module 3

gmv-03.ppt © ESI April 2015 3-25

Agile Roles

Module 3

gmv-03.ppt

The Product Owner

• Responsible fordelivery of value fromthis product

• “One voice” of thecustomer

• Prioritises and ownsProduct Backlog

• Available anddedicated

• Empowered• Servant-Leader

© ESI April 2015 3-26

Module 3

gmv-03.ppt

The Team Lead

• Similar to “Scrum Master”• Ensures that everyone is following the “team rules”• Facilitator• Servant-Leader, not a “controller”• Enables the Team Members to self-organise• Monitors and reports on progress• Removes impediments• If full-time inappropriate, may be a Team Member with

additional responsibility

© ESI April 2015 3-27

Scrum Master

Module 3

gmv-03.ppt

The Team Members

• 5 to 9 people who deliver what they say they will• Includes all skills required for delivery• Self-organising• Motivated• Mutually accountable and responsible – “Generalising

Specialists”• Sustainable pace• Delivers incrementally• Works iteratively• Ideally co-located

© ESI April 2015 3-28

Module 3

gmv-03.ppt

T- Shaped Skills

Core Skillset

Broad Knowledge

© ESI April 2015 3-29

Module 3

gmv-03.ppt

Core Skillsets

Broad Knowledge

© ESI April 2015 3-30

TT- Shaped Skills

Module 3

gmv-03.ppt

The Architecture Owner

• Owns the view of the overall solution • Technical and domain expert • Supports requirements envisioning • Architecture is evolutionary • Not a hierarchical position – a facilitative leader, not

command and control • Owns architecture decisions • An active developer • Encourages better design • Not the Product Owner

© ESI April 2015 3-31

Module 3

gmv-03.ppt

Stakeholders • Those who influence or are impacted by the work and its outcomes • Remember to consider

– Users o Internal o Public o Persona

• Run The Bank (RTB) • Production • DevOps • Change Teams • GTIS • Line Management • HR

– Collaborators, not “them and us”

© ESI April 2015 3-32

Module 3

gmv-03.ppt

Specialists

• May be required on complex pieces of work • Can help us explore requirements • Examples:

– DBAs – Security Analysts – Business SMEs

• May include Programme Management on large scale projects

• Integration Specialists

© ESI April 2015 3-33

Module 3

gmv-03.ppt

Domain Expert

• Provides further expertise to the Product Owner • May be required on complex pieces of work • Can help us explore requirements

© ESI April 2015 3-34

Module 3

gmv-03.ppt

Technical Expert

• Temporary Team Members • Provide short-term technical skills and knowledge • Should seek to transfer skills to generalising specialist

Team Members • May include expertise in regulatory or compliance

matters

© ESI April 2015 3-35

gmv-04.ppt

Module 4

Goals of the Construction Phase

• Produce a potentially consumable solution• Address changing stakeholder needs• Move closer to deployable release• Maintain or improve upon existing levels of quality• Prove architecture early


gmv-04.ppt

Module 4



gmv-04.ppt

Module 4

The Iteration

• The Iteration is an Agile “Event” • It is also the container for all other Agile Events • Work progresses in Iterations until the Product Owner is

satisfied that either – The product is complete – Sufficient value has been delivered for the work to

cease • Iterations should be of consistent duration within the

constraints of 1 to 4 weeks (shorter often preferred) • Iterations are “Timeboxed” • Target is “Potentially Shippable (or Releasable)

Product”– Product Owner decides


gmv-04.ppt

Module 4

Agile Events

• The Iteration • Iteration Planning • Daily Stand-Up • Iteration Review • Iteration Retrospective


gmv-04.ppt

Module 4

Iteration Planning

• First part – the “Whats” • Second part – the “Hows” • Iteration Backlog – a “pulled” list

– Owned by the development team – They jointly commit to delivering the Iteration Backlog – No individual ownership – work as a team – Describes the scope of the Iteration


gmv-04.ppt

Module 4

Iteration Planning Exercise

• In your teams, you will build an Iteration Backlog for the first Iteration

• You may need to break down some of your Epics into User Stories

• Use your Release Plan as a guide • Preparation time: 15 mins • Presentation time: 5 mins per team


gmv-04.ppt

Module 4

Daily Stand-Up

• Timebox 15 mins • Development Team and

Team Lead participate • Product Owner may

silently observe • Three questions

– What did I do since the last Daily Stand-Up?

– What will I do before the next Daily Stand-Up?

– Are there any impediments in my way?

• All other matters to be addressed outside the Daily Stand-Up


gmv-04.ppt

Module 4

Iteration Review

• Whole Agile team and wider stakeholder community • How are we doing? • Is the product of this Iteration as expected? • Do you have any comments or questions regarding the

product that we should know? • Is the Product Backlog fully prepared for the following

Sprint Planning session? • Is this work still viable? Are we still a good investment?


gmv-04.ppt

Module 4

Iteration Retrospective

• Development Team, Team Lead • Optional Product Owner • Not Stakeholders / Users • A time for the team to reflect on its performance • Can be challenging! • An opportunity to improve both the team and organisation • Review the successes and challenges of using an Agile

approach • “Clear the air” in case of disagreement


gmv-05.ppt

Module 5

Agile Transition

• Part of the work of the Team • Team includes all skills and knowledge required to deliver

in line with the definition of “Done” • Specialist assistance may be required from time to time • Goal is

– 80% automated test (established Agile teams) – Automated release


Module 6

gmv-06.ppt

Next Steps

• This course is the gateway to further career and personal development opportunities

• You should try to continue to learn about the BACL and Agile

• You may be offered further training in Agile by the bank – select and agree on the most relevant training

• Your local Agile champion will be able to provide support


Module 6

gmv-06.ppt

Get in touch with your Business Unit Agile Champions

Follow CoP on MySite http://agilecop/

Join CoP events, for example Lean Coffee

Agile Page: http://agile/


Barclays Agile Resources

Module 7

gmv-07.ppt

Course Closeout

• Any final comments / questions about Agile? • Any observations regarding this course or trainer? • Do you feel that this course has offered value to you and

the bank?


Module 7

gmv-07.ppt

End of Course

• Thank you very much for attending this course • We hope to see you again in the future


agile@barclays - elearning.esi-intl.comelearning.esi-intl.com/blendedlearning/ilt/gmv001... ·...

Documents