• Save
Agile basics
Upcoming SlideShare
Loading in...5
×
 

Agile basics

on

  • 412 views

Short introduction to Agile focusing on 5 of the core practices

Short introduction to Agile focusing on 5 of the core practices

Statistics

Views

Total Views
412
Views on SlideShare
387
Embed Views
25

Actions

Likes
2
Downloads
0
Comments
0

5 Embeds 25

https://twitter.com 15
http://www.1agile.com 4
http://1agile.com 4
http://54.187.9.213 1
https://www.linkedin.com 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Agile basics Agile basics Presentation Transcript

    • allan kelly Twitter: @allankellynet http://www.allankelly.net Agile Basics webinar June 2014
    • Allan Kelly…  Author  Software Development Consultant  Training for Agile Books – Changing Software Development: Learning to be Agile (2008) – Business Patterns for Software Developers (2012) – Xanpan: Team Centric Agile Software Development (2014) http://www.xanpan.org Xanpan eBook (LeanPub) Xanpan printed book (Lulu)
    • Focus on (just) 5 Agile Basics • Quality • Visualize work • Iterations • Work in the small (batch size) • Vertical Teams
    • Quality Build in Quality Bug prevention Keep code maintainability
    • Capers Jones, 2008 Applied Software Measurement the cost of repairing defects is the most expensive single activity [in software development]. • Defects are expensive – Very expensive • Defects destroy schedules • Defects destroy predictability • Defects destroy trust
    • Invest in quality, invest in code Test Driven Development (TDD) Test First Development, Design Driven Development, Automated Unit Testing Acceptance Test Driven Development (ATDD) Behavior Driven Development (BDD) Continuous Integration (CI) (Pair programming)
    • Invest in technical practices to save money Spend a little Save a lot
    • Visualize See the work See to learn
    • Use a whiteboard daily
    • Use a board tomorrow
    • Graph the work 0 50 100 150 200 250 1 2 3 4 5 6 7 8 9 10 11 12 Iteration Basic Product Burn-Down Chart Work to do
    • Use information rich charts 0 20 40 60 80 100 120 140 0 1 2 3 4 5 6 7 8 9 10 11 12 13 Iteration Work to do Total done Released
    • Iterations
    • Iterations repeat Continually Iterations impose regular deadlines and limit work in progress Iterations create rhythm and regularity
    • Humans are bad at estimating time Humans are good at working to deadlines Fit the work to the time Work to the deadline
    • Thursday Friday Monday Tuesday Wednesday Iteration - 2 week routine Thursday Friday Monday Tuesday Wednesday Work Release Demo Prioritization Breakdown Agreement
    • Thursday Friday Monday Tuesday Wednesday Everything in Iteration Thursday Friday Monday Tuesday Wednesday Releasableatend ofIteration To release or not is a business decision Programmers: Coding, Design & Unit Testing Product Owner: Requirement discover & explanation Testers: Automated & Exploratory testing
    • Releasable at the end of the iteration Is more important Then Released
    • First Base Releasable product every 2nd Thursday Give business options Go No Go
    • Iterations alone make you better Fixing all the things that stop you working in iterations, slow you down or prevent 2 weekly releases will make you far far better still. More importantly
    • Small
    • Software development does not have economies of scale Software development has dis-economies of scale
    • Milk is cheapest in BIG cartons Software is cheapest in lots of small cartons Small cartons of software also reduce the risk
    • Work in the small Software development does not have economies of scale Software development has dis-economies of scale For software bigger means more expensive & more risk
    • Lots and lots of small steps Keep It small Get good at working in the small
    • Small Small tests Small pieces of code Small stories for development Small tasks for work Small releases Short iterations Get good at small
    • Teams
    • Effective Teams Vertical teams Fully staff (all the time) Devolve decision making Keep teams together Flow the work to the team
    • Horizontal Teams Business Logic Database Test User Interface Business Analysis
    • Vertical Teams
    • Programme manager Project Manager Architect Analyst Team Lead Dev 1 Dev 2 Tester Hay! Should this be blue or red? Let me find out… Let me escalate that… Red Delay Delay Delay Delay Delay Delay
    • Devolve decisions to the team to speed up decision making
    • We should talk more…. Customer involvement Requirements & Specifications Retrospectives Planning Testing Stand-up meetings ….
    • Any 1 of these points will make you better Doing the all 5 is even better Doing even more is better still!
    • 1. Invest in quality 2. Visualize work 3. Get good at iterations 4. Work in the small 5. Vertical teams 5 Basics allan kelly @allankellynet allan@allankelly.net http://www.xanpan.org - http://leanpub.com/xanpan ½ price until 16 June https://leanpub.com/xanpan/c/June04Webinar