Short agilefordba

345 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
345
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Short agilefordba

  1. 1. Quick Agile Introduction 1 ©2007 - 2012 Octopus Software LLC, All Rights Reserved
  2. 2. Linear Progress: Winners in High Jump Fosbury 2.5 Flop 2.0 Straddle Western 1.5 Roll Scissors 1.0 1900 1920 1940 1960 1980 William F Achtmeyer Center for Global Leadership-Tuck School of Business at Dartmouth 2 ©2007 - 2012 Octopus Software LLC, All Rights ReservedThis shows a linear improvement but with some disruptive context. You can see general improvement, but notice that a jumper using scissortechnique, even if they are the “best”, can’t win against a similarly talented person using the Fosbury Flop. This is the improvement treadmill thatwe are on to survive as an organization.
  3. 3. What is Agile? -ManifestoFrom: www.agilemanifesto.org:• Individuals and interactions over processes and tools• Working software over comprehensive documentation• Customer collaboration over contract negotiation• Responding to change over following a planThat is, while there is value in the items onthe right, we value the items on the left more. 3 ©2007 - 2012 Octopus Software LLC, All Rights Reserved
  4. 4. What is Agile? From: www.agilemanifesto.org/principles.html • 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. • Working software is the primary measure of progress • 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. 4 ©2007 - 2012 Octopus Software LLC, All Rights ReservedHave the students listen to each of the principles. Ask them to pick a top 3 that their group or boss could get the most benefit from?
  5. 5. Common Issue: • Local optimization is the tuning of one part of the work flow in a way that impedes the overall work flow Inventory - Handoff and DelayProject Flow ArchitectureAnalysis Design Dev TestWhat if everyone was on the same team? 5 ©2007 - 2012 Octopus Software LLC, All Rights Reserved
  6. 6. Agile Flow Stories Packaged Team Team For QA g nin System an Pl Iteration o Iteration Test r se Ze lea Review s Planning on on Re ati ati r r Ite Ite Update Backlog Release Estimates Approved Tasks + And Moved Capacity Plan Estimates Tested + Accepted To Prod Initial Priorities Implementation Stories Backlog Production Verification Feasibility + Portfolio Timeframes Planning Business Need Operational + Budget Feedback 6 ©2007 - 2012 Octopus Software LLC, All Rights ReservedThis diagram give the instructor a chance to talk about how Iteration Planning fits into the overall project.This is the second planning step in an agile project.This plan outlines which capabilities/ features are going to be developed in which iteration.The processes reconciles conflicting priorities that the team may have.Key players are the business owners, iteration manager, tech lead and test lead. (If the business person is not there, the meeting is postponed.).
  7. 7. High Level Agile Factory VelocityProjectBacklog One Cycle Story Story Story Story Story Story Story Story 1 1 2 2 1 ADDT 1 2 2 Story Story Story Story Story Story Story Story Story Story Story Story CapacityCompleted 2 2 4 4 2 2 1 ADDT 1 1 1 1 1 Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story 2 2 2 2 2 2 2 2 2 ADDT 1 2 1 4 4 2 2 2 2Outstanding Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story 4 4 1 1 2 2 2 2 4 ADDT 2 4 2 1 1 2 2 2 2 Week 3 5 7 9 11 13 15 17 19 Iterations 6 6 4 8 9 4 8 4 4 Velocity - Actual Planned (^Thanksgiving) Last 2 iterations Original Backlog - 53 points Now Release Evolving Design Preparation System + Performance Test 7 ©2007 - 2012 Octopus Software LLC, All Rights Reserved
  8. 8. Timing Differences Iteration #1 (2 weeks) Iteration #2 (2 weeks) High Level Requirements Story #5 Detail Story #10 Detail Story #6 Detail Story #11 Detail Story #7 Detail Story #12 Detail Story #8 Detail Story #13 Detail Story #9 Detail Story #14 Detail Review/ Update Architecture Review / Update Design, Config Build Story #1 Build Story #5 Build Story #2 Build Story #6 Build Story #3 Build Story #7 Build Story #4 Build Story #8 Build Story #15 Build Story #9 Continuous System Testing Build = Analysis, Design, Test, Construction, Code Review and Acceptance Test 8 ©2007 - 2012 Octopus Software LLC, All Rights ReservedKey timing differences:“What many groups do in months many agile teams can do in 2 days”1. Start with very high level requirements, commonly in the form of stories.2. Stories are detailed with acceptance criteria, with are the requirement details3. Architecture is simplified, primarily technology curbs to limit choices teams have4. Coding starts within weeks, which includes design and acceptance tests5. System tests begins within weeks
  9. 9. Questions for DBA Work• Issues: – How do I know the context of requests? – What are my priorities? Which work should get done first? – What are the impacts of the requested change? – How do I change what is requested?• Good reference at www.agilemodeling.com (Scott Ambler) 9 ©2007 - 2012 Octopus Software LLC, All Rights Reserved

×