being agile about agile

36
Project Andiamo Being Agile With Agile For Lovely People at Bethnal Green Ventures

Upload: naveed-r-parvez

Post on 27-Jan-2015

139 views

Category:

Business


3 download

DESCRIPTION

A real world overview of Agile methodologies

TRANSCRIPT

Page 1: Being agile about agile

Project Andiamo

Being Agile With AgileFor Lovely People at Bethnal Green Ventures

Page 2: Being agile about agile

Project Andiamo

We’ll Cover

• Quick history

• What is Agile in the real world

• Two methodologies called Scrum and Kanban

Page 3: Being agile about agile

Project Andiamo

Disclaimer

This is what I’ve learnt not textbook says I swear a lot

Page 4: Being agile about agile

Project Andiamo

A Brief Historyhttp://www.senseoncents.com/wp-content/uploads/2012/07/Declaration-of-Independence1.jpg

On February 11-13, 2001, mountains of Utah, seventeen people met to talk, ski,. What emerged was the Agile Software Development Manifesto. Representatives from Extreme Programming, !Now, a bigger gathering of organizational anarchists. !The only concern with the term agile came from Martin Fowler most Americans didn’t know how to pronounce the word agile.

Page 5: Being agile about agile

Project Andiamoagilemanifesto.org

Page 6: Being agile about agile

Project Andiamo

12 Principles of Agile• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

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

• Deliver working software 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 daily throughout the project.

• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

• The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

• Working software 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 behavior accordingly.

Page 7: Being agile about agile

Project Andiamo

Adaptive Vs Predictive

Page 8: Being agile about agile

Project Andiamo

Shit happens so stop pretending

Page 9: Being agile about agile

Project Andiamo

That doesn’t mean you don’t plan

Page 10: Being agile about agile

Project Andiamo

You plan around being wrong

Page 11: Being agile about agile

Project Andiamo

If you’re building something new you’re free climbing

We had to persuade the business that they didn’t know where they were going they just broadly knew the destination

Page 12: Being agile about agile

Project Andiamo

Types of Agile• Adaptive Software Development (ASD)

• Agile Unified Process (AUP)

• Crystal Methods (Crystal Clear)

• Dynamic Systems Development Method (DSDM)

• Extreme Programming (XP)

• Feature Driven Development (FDD)

• Kanban

• Lean software development

• Scrum

• Scrum-ban

Page 13: Being agile about agile

Project Andiamo

Scrum

"a flexible, holistic product development strategy where a development team works as a unit to reach a common goal"

as opposed to a "traditional, sequential approach".

Page 14: Being agile about agile

Project Andiamo

Scrum

http://glenndejaeger.files.wordpress.com/2011/01/scrum_large.png

Page 15: Being agile about agile

Project Andiamo

http://cd.executivebrief.com/img/a468-f1-scrum-team.gif

Page 16: Being agile about agile

Project Andiamo

http://www.kennethvr.be/blog/wp-content/uploads/scrumRoles2.jpg

Page 17: Being agile about agile

Project Andiamo

http://mazzive.com/blog/wp-content/uploads/2009/02/scrum_process_feedback1-1023x308.png

Retrospective

Page 18: Being agile about agile

Project Andiamo

http://soenkerohde.com/img/My_Demo_Project_-_Pivotal_Tracker-20090426-165717.png

Story Points

Page 19: Being agile about agile

Project Andiamo

When is it good?• Your team works together in the same place at the

same time

• Multiple development teams

• Defined roles

• You need discipline

• Corporates/Customers: It feels more processey

Page 20: Being agile about agile

Project Andiamo

Kanban

http://availagility.files.wordpress.com/2008/10/kenji-kanban-2.jpg

Toyota Just in time manufacturing

Page 21: Being agile about agile

Project Andiamo

http://www.toyota.eu/SiteCollectionImages/Society/The%20Toyota%20Way_500.jpg

Kaizen - Improvement or Change for the best Genchi Genbutsu - go and see

Page 22: Being agile about agile

Project Andiamo

http://a3.southwestsolutions.com/images/gallery/two-bin-medical-supply-kanban-nursing-unit-stock-replenish-system-sku-increase-inventory-management-plastic-wire/2-bin-kanban-medical-system-supplies-restrock-stockcard-nursing-units-replenish-room-

concept.jpg

Kaizen - Improvement or Change for the best Genchi Genbutsu - go and see

Page 23: Being agile about agile

Project Andiamo

http://conroyquick.files.wordpress.com/2011/09/toilet-kanban.jpg

Kaizen - Improvement or Change for the best Genchi Genbutsu - go and see

Page 24: Being agile about agile

Project Andiamo

http://www.naomiblogs.com/wp-content/uploads/2010/08/P1000274.jpg

Page 25: Being agile about agile

Project Andiamo

Principles 1. Visualise 2. Cards 3. WIP limit

Page 26: Being agile about agile

Project Andiamo

Difference between done and successful

Page 27: Being agile about agile

Project Andiamo

http://alphagov.files.wordpress.com/2012/10/img_4810.jpg%3Fw%3D553%26h%3D415

Principles 1. Visualise 2. Cards 3. WIP limit

Page 28: Being agile about agile

Project Andiamo

Push Vs Pull

We agreed to be available together 1 entire day each week Blockage meetings

Page 29: Being agile about agile

Project Andiamo

SCRUM

http://glenndejaeger.files.wordpress.com/2011/01/scrum_large.png

Page 30: Being agile about agile

Project Andiamo

Kanban

http://glenndejaeger.files.wordpress.com/2011/01/scrum_large.png

Page 31: Being agile about agile

Project Andiamo

When is it good?

• Your team is in different places and works at different times

• Experienced and confident team

• No politics

You can lay Kanban over the top of SCRUM Kanban itself is not a software development process

Page 32: Being agile about agile

Project Andiamo

http://www.jsmorin.com/2013/11/4-ways-to-measure-in-fantasy/

Story points Velocity Burndown People Hours

Page 33: Being agile about agile

Project Andiamo

Principles I’ve Learnt• Users first

• Use cases are mandatory

• We aim to fail fast

• We will make mistakes, we accept this and mitigate losses up front

• Everything we build is

• Quickly iterative

• Disposable

• Doesn't constrain future growth

• Agnostic

• We always test (e.g. TDD, BDD) but real world tests are more important

• The value in the future is context. How we get insights, make better decisions, and tell stories with that data

Page 34: Being agile about agile

Project Andiamo

One Question

Page 35: Being agile about agile

Project Andiamo

What is the fastest, cheapest, and best way to screw this up?

All these things are just tools they won’t stop you screwing stuff up

Page 36: Being agile about agile

Project Andiamo

Now iterate