Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

IT Agility Makes Work Fun Again

In every situation there are significant improvements that can be made in 30 days or less; they become your base for building further capabilities as you move towards your goal. Identify the most important capabilities needed; focus activity on delivering a “Robust 80% Solution”. Then continue to enhance the application as the world unfolds…

  • Be the first to comment

IT Agility Makes Work Fun Again

  1. 1. IT Agility Makes Work Fun Again [The 30-Day Blitz in Action] Michael Hugos Center for Systems Innovation [c4si]
  2. 2. What is the Agile 30-Day Blitz? © 2013, Michael Hugos www.MichaelHugos.com 2 Center for Systems Innovation [c4si]
  3. 3. The Agile 30-Day Blitz • In every situation there are significant improvements that can be made in 30 days or less; they become your base for building further capabilities as you move towards your goal • Quickly identify handful of most important capabilities needed; focus activity on delivering a “Robust 80% Solution” • Continue to enhance system as world unfolds… © 2013, Michael Hugos www.MichaelHugos.com 3 Center for Systems Innovation [c4si]
  4. 4. Blitz is Focused, Iterative Approach • Think big, start small, deliver quickly! Blitz 3 • First blitz delivers working system that is “Robust 80% Solution” • Succeeding blitzes enhance system with additional features Blitz 2 Blitz 1 • System grows in response to most pressing business needs © 2013, Michael Hugos www.MichaelHugos.com 4 Center for Systems Innovation [c4si]
  5. 5. 30-Day Blitz Timeline DEFINE Process Deliverables DESIGN Process Deliverables • Business Goal & Performance Requirements BUILD • New Business Process Flows • Conceptual System Design • Cost/Benefit Analysis • Initial Plan & Budget • System Data Model • Prototype of User Interface & Tech Architecture • Actual Plan & Budget 2 Days Process Deliverables • Working System that Meets Requirements • Tech Documentation & User Manual 7 Days 13 Days [There are 22 working days in a typical 30-day period] © 2013, Michael Hugos www.MichaelHugos.com 5 Center for Systems Innovation [c4si]
  6. 6. Seven Core Techniques 1. Joint Application Design – ideation and brainstorming to pool a team’s collective ideas and insights 2. Process Mapping – drawing out existing work flows and designing new ones (user stories are collections of processes) 3. Data Modeling – defining types and volumes of data the app will handle 4. System Prototyping – modeling the user interface and the technical architecture 5. Object Oriented Design & Prgmg – creating systems and apps from libraries of pre-defined software components 6. System Test & Rollout (DevOps) – debugging and tweaking apps, rolling them into production and training people to use them 7. Agile Project Management – coordinating project tasks and spotting problems and dealing with issues as they arise on the project © 2013, Michael Hugos www.MichaelHugos.com 6 Center for Systems Innovation [c4si]
  7. 7. Blitz Calendar Mon DEFINE Week 2 DEFINE Agility W/S Agility W/S Orient Team; Plan Project DESIGN Week 1 Tue DESIGN DESIGN Workflows, data model, UI JAD #2 Wed Thu Fri DESIGN DESIGN DESIGN JAD #1 DESIGN Sat Workflows, data model, UI BUILD Finish design and Finish design and Object models, tech arch tech arch update proj plan BUILD Week 4 Week 5 BUILD BUILD BUILD BUILD Object models, update proj plan BUILD Coding, create test scripts BUILD Coding, create test scripts BUILD Coding, create test scripts BUILD Coding and testing BUILD Coding and testing Coding and testing Coding, testing, documentation Coding, testing, documentation Coding, testing, documentation BUILD Week 3 Sun BUILD SYSTEM Coding, testing, documentation Coding, testing, documentation DEMO Shape the work to fit within these time boxes – weekends are for relaxing… Agility is simple things done well, not complex things done fast. © 2013, Michael Hugos www.MichaelHugos.com 7 Center for Systems Innovation [c4si]
  8. 8. How is it Done? © 2013, Michael Hugos www.MichaelHugos.com 8 Center for Systems Innovation [c4si]
  9. 9. DEFINE the System (2 Days) • Business goal is target you aim for • Conceptual system design embodies strategy to accomplish business goal • Break conceptual design into system development objectives • Calculate initial budget by estimating cost to achieve each development objective * Core techniques used: joint application design; process mapping; data modeling © 2013, Michael Hugos www.MichaelHugos.com GOAL - Devise strategy that maximizes use of company’s existing strengths - Express strategy as conceptual design for using people, process, & technology PEOPLE PROCESS TECHNOLOGY Objective A Objective B Objective C Objective D - Define necessary & sufficient set of objectives to build conceptual system 9 Center for Systems Innovation [c4si]
  10. 10. Business Action Framework The Goal is the Target – two sentences or less stating the action and desired result Business Functions Objective 1 Critical Objectives – the handful of measurable actions that are necessary and sufficient to accomplish the Mission GOAL Objective 2 Objective 3 Objective 4 Grade Prospecting C-2 Order Entry B-3 Customer Service A-2 Production Scheduling D-2 Business functions impacting the most critical objectives and with the lowest grades are the bottlenecks. Improvements there deliver the greatest benefits in the shortest time. © 2013, Michael Hugos www.MichaelHugos.com 10 Center for Systems Innovation [c4si]
  11. 11. Conceptual System Design – the Key • GOAL: what is the business goal of the blitz? (action leading to some desired result) • PERFORMANCE REQUIREMENTS: what performance targets must the solution system achieve? • SYSTEM COMPONENTS: what are the handful of components you will use to build the solution system? • SYSTEM SCHEMATIC: draw a simple diagram showing these system components and how they work together to meet the necessary performance requirements © 2013, Michael Hugos www.MichaelHugos.com 11 Center for Systems Innovation [c4si]
  12. 12. Conceptual Design Example GOAL: Develop end-to-end quality system by integrating data across the business to enable improvement of customer satisfaction and product quality for game console. Version 1.0 system delivered in 30 days; second blitz delivered further features and enhancements SYSTEM COMPONENTS: • Existing system data sources • Batch Data Transfer • Central database3 • Web pages • Data query & reporting package • Small custom pgms © 2013, Michael Hugos www.MichaelHugos.com Returns Tracking Web Console B.O.M. Data Load Console Sales Query Central Database & Report Tools Online Network 12 Center for Systems Innovation [c4si]
  13. 13. DESIGN the System (7 Days) Goal & Objectives • Project teams assigned to each objective use core techniques* to create detailed designs and technical specifications • Detailed specifications enable creation of detailed plan and budget for system development A Process Diagrams * Core techniques used: joint application design; process mapping; data modeling; system prototyping; agile project management © 2013, Michael Hugos www.MichaelHugos.com B C D Logical Data Model System Prototype Project Plan & Budget Objective A Task 1 Task 2 Task 3 Objective B Task 4 Task 5 Objective C Task 6 Task 7 Total Project 13 Cost $999 $99 $999 ___ $9999 Center for Systems Innovation [c4si]
  14. 14. Five Questions Every Day Key questions for morning standup meetings: 1. Has the scope of any project task changed? (Yes/No) 2. Will any major activity or milestone date be missed? (Yes/No) 3. Does project team need any outside skills or expertise? (Yes/No) 4. Are there any unsolved technical problems? (Yes/No) 5. Any unresolved user review or approval problems? (Yes/No) For all questions marked Yes, briefly explain the problem and recommend possible solutions Update project plan in light of these answers; add any new tasks; adjust tasks as necessary to stay in time boxes © 2013, Michael Hugos www.MichaelHugos.com 14 Center for Systems Innovation [c4si]
  15. 15. BUILD the System (13 Days) Project Plan & Budget Objective A Task 1 Task 2 Task 3 Objective B Task 4 Task 5 Objective C Task 6 Task 7 Total Project • Every day re-calculate time and budget needed to complete each objective • Manage project scope and allocate resources so as to achieve objectives on time and on budget $99 $999 ___ $9999 Logical Data Model System Prototype Object Model • Get version 1.0 of system into production ASAP – then add additional features as business needs arise Development * Core techniques used: object oriented design and programming; system test and rollout; agile proj mgmt. © 2013, Michael Hugos www.MichaelHugos.com Cost $999 Environment Roll Out 15 Center for Systems Innovation [c4si]
  16. 16. Lessons Learned • Focus on “Robust 80% Solution” – let go of perfection • Minimize custom coding by integrating existing system components • Run work in parallel to build system components • Assign teams of 2-7 developers to each system component • Need project management support or else teams handle change with personal to-do lists and coordination suffers • System builder needs strong skills in listening, consensus building and problem solving – both business and technical • Production roll out and security audit handled between blitzes • Focus on “HOW WE CAN” (not “Why we can’t”) © 2013, Michael Hugos www.MichaelHugos.com 16 Center for Systems Innovation [c4si]
  17. 17. Learn More… Presentation excerpted from my book: Briefing management in agile strategies; mentoring teams in agile development Center for Systems Innovation [c4si] www.MichaelHugos.com Strategically Focused and Tactically Agile CIO, 2013 ebook and paperback - http://www.amazon.com/Strategically-Focused-Tactically-Agile-ebook/dp/B004PLO65K/ © 2013, Michael Hugos www.MichaelHugos.com 17 Center for Systems Innovation [c4si]

    Be the first to comment

    Login to see the comments

  • AkbarMohammadLou

    Feb. 19, 2015

In every situation there are significant improvements that can be made in 30 days or less; they become your base for building further capabilities as you move towards your goal. Identify the most important capabilities needed; focus activity on delivering a “Robust 80% Solution”. Then continue to enhance the application as the world unfolds…

Views

Total views

948

On Slideshare

0

From embeds

0

Number of embeds

2

Actions

Downloads

18

Shares

0

Comments

0

Likes

1

×