DOCSLIB.ORG

1 Thursday, April 1, 2010

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
1 Thursday, April 1, 2010 Thursday, April 1, 2010 1 Beyond Scrum © 2010 Clinton Keith Consulting Thursday, April 1, 2010 2 Clinton Keith - Background Agile coach and Scrum trainer 24 years of development experience 14 years of game development experience 7 years of agile development experience in the game industry Introduced agile to the industry in March 2005 3 Thursday, April 1, 2010 Beyond Scrum • Filling out the framework • Appling project management practices where needed • Using common sense, not dogma No rules, just shared practices © 2010 Clinton Keith Consulting Thursday, April 1, 2010 4 Games Recently Shipped That Used Scrum © 2010 Clinton Keith Consulting Thursday, April 1, 2010 5 Game Development Challenge • Manage • Fixed ship dates • Minimum required feature sets • Long project cycles with production • While avoiding crunch © 2010 Clinton Keith Consulting Thursday, April 1, 2010 6 Fixed Ship Dates © 2010 Clinton Keith Consulting Thursday, April 1, 2010 7 The Project Management Triangle Scope Product Backlog Schedule Cost (resources) Velocity © 2010 Clinton Keith Consulting Thursday, April 1, 2010 8 Better & Cheaper & Faster © 2010 Clinton Keith Consulting Thursday, April 1, 2010 9 Velocity & Fixed Schedules Brooks’s Law: Scope “Adding manpower to Goal a late software project makes it later” Deadline!Fred Brooks (1975) Resources Crunch, Extra people Time © 2010 Clinton Keith Consulting Thursday, April 1, 2010 10 There are often scope limits • Minimum marketable features • Cutting scope by 50% to meet a date may produce a product that won’t sell • Example: A Word Processor without a printing feature © 2010 Clinton Keith Consulting Thursday, April 1, 2010 11 Minimum Marketable Features = RISK + Fixed Schedule © 2010 Clinton Keith Consulting Thursday, April 1, 2010 12 Applying PM, Attacking Risk • Identify minimum marketable feature set • MuSCoW analysis • Identify critical paths • Example: Game running on the PS3 • Identify path risks • Example: Graphics throughput on the RSX • Prioritize work based on risk • E.g. Spike to demonstrate demo level on PS3 with maximum desired detail • Find and address bad news early • Example: Need to create lower resolution levels © 2010 Clinton Keith Consulting Thursday, April 1, 2010 13 High Value !"#$%&"' !"#$%&"' !"#$%&"' (")*+,' -./"01))"$' ("2%+03%,"' !"#$%&"' !"#$%&"' Low !"#$%&"' Value Progress © 2010 Clinton Keith Consulting Thursday, April 1, 2010 14 MuSCoW Analysis Must Have Should Have Could Have Won’t Have © 2010 Clinton Keith Consulting Thursday, April 1, 2010 15 Minimum Required Feature Set Must Haves • Example: Console FPS • 8 + hours single-player campaign • Online multiplayer • XBox 360 • PS3 Dropping any of these means failure © 2010 Clinton Keith Consulting Thursday, April 1, 2010 16 Minimum Required Feature Set Should Haves • Example: Console FPS • Cooperative Online Multiplayer These add great value, but aren’t absolutely necessary © 2010 Clinton Keith Consulting Thursday, April 1, 2010 17 /97:8"'*8#;"&' 67897"'-.' 12)3045' ./0' <"=9:7' ())*"&#+,"'-.' ()>"?@=="$' <"2%:?A%7"' !"#$%&"' !"#$%&"' !"#$%&"' !"#$%&"' © 2010 Clinton Keith Consulting Thursday, April 1, 2010 18 Backlog Prioritization Value Cost Risk Knowledge © 2010 Clinton Keith Consulting Thursday, April 1, 2010 19 Risk Prioritization © 2010 Clinton Keith Consulting Thursday, April 1, 2010 20 Critical Path • The things that need to happen, in sequence. • Usually dependent on one another PS3 Critical Path Development Engine Game Performance Multiplayer Environment Running Running ??? Subcontractor © 2010 Clinton Keith Consulting Thursday, April 1, 2010 21 Critical Chain Staffing PS3 Single Player (6 people x 10 (20 people x 12 months) months) Xbox 360 (4 people x 16 Multiplayer months) (12 people x 8 months) Cooperative MP (4 people x 6 months) © 2010 Clinton Keith Consulting Thursday, April 1, 2010 22 Putting it all together • Have dedicated people/teams/time for each major feature • Have them work off their own backlog • Watch out for • Inconsistent progress • Great Multiplayer, bad single player • “Feels like” different experiences • Not enough sharing • Example: Multiplayer on the PS3 © 2010 Clinton Keith Consulting Thursday, April 1, 2010 23 Production Risk © 2010 Clinton Keith Consulting Thursday, April 1, 2010 24 Agile is phase-less Iteration Iteration Iteration Design Design Design Code Code Code Create Assets Create Assets Create Assets Debug & Tune Debug & Tune Debug & Tune ...is game development? © 2010 Clinton Keith Consulting Thursday, April 1, 2010 25 Not Quite 100% Production 75% Development Design Concept 50% 25% 0% Alpha/Beta Production #1 Production #2 Production #3 Production #4 Pre-ProductionPre-Production #1 Pre-Production #2 #3 We have stages © 2010 Clinton Keith Consulting Thursday, April 1, 2010 26 Production is Debt Deadline! Production Start Date! Pre-Production Production Sure...why not... Crunch Pre-ProductionPre-Production ProductionProduction © 2010 Clinton Keith Consulting Thursday, April 1, 2010 27 Schedule Probabilities Date? Probability Date of (peak, not mean) Completion Time © 2010 Clinton Keith Consulting Thursday, April 1, 2010 28 Refining Production Dates Deadline! Pre-Production Production ProductionProduction © 2010 Clinton Keith Consulting Thursday, April 1, 2010 29 Selecting the right tools for pre-production and production © 2010 Clinton Keith Consulting Thursday, April 1, 2010 30 Process tools driven by certainty Far from Agreement Anarchy Complex Requirements Scrum (fun) Complicated Lean Pre-production Simple Close to Production Agreement Close to Far from Certainty Technology Certainty Iterative Source: Strategic Management and Organizational az by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle. Incremental © 2010 Clinton Keith Consulting Thursday, April 1, 2010 31 Lean/Kanban Deadline! Kaizen Work Uncertainty Time © 2010 Clinton Keith Consulting Thursday, April 1, 2010 32 More on Kanban... November 2008 feature article in Gamasutra Chapter in upcoming book © 2010 Clinton Keith Consulting Thursday, April 1, 2010 33 Common sense © 2010 Clinton Keith Consulting Thursday, April 1, 2010 34 Don’t follow labels ScrumBan Lean Kanban XP Scrum Lean-Agile © 2010 Clinton Keith Consulting Thursday, April 1, 2010 35 • Scrum isn’t the goal • Following the rules no matter what • Focus on the principles • Empiricism - Science vs. alchemy • Emergence • Time-Boxing • Prioritization • Self-Organization • Iterate on the process • Provide leadership • Plan, plan, plan © 2010 Clinton Keith Consulting Thursday, April 1, 2010 36 Summary. Changes. Iterate and we’ll Devs given suspect measure velocity dates & crunch towards the goal Devs solely responsible Biz is responsible for for achieving the goal achieving the goal Delivery of We’ll optimize resources Completion of activities features Devs make biz Devs make dev decisions, biz makes decisions, biz makes dev decisions biz decisions © 2010 Clinton Keith Consulting Thursday, April 1, 2010 37 Clinton Keith [email protected] www.ClintonKeith.com Questions? © 2010 Clinton Keith Consulting Thursday, April 1, 2010 38.
Load more

Recommended publications
  • Improving Software Development Through Combination of Scrum and Kanban
    Recent Advances in Computer Engineering, Communications and Information Technology Improving Software Development through Combination of Scrum and Kanban VILJAN MAHNIC Faculty of Computer and Information Science University of Ljubljana Trzaska 25, SI-1000 Ljubljana SLOVENIA [email protected] Abstract: - Applying Kanban principles to software development is becoming an important issue in the area of software engineering. The number of Scrumban users, a method that combines Scrum and Kanban practices, almost doubled in the last year. While Scrum is well-known and widespread method, scientific literature about Kanban adoption is scarce and many questions regarding Kanban use in practice (e.g., the structure of Kanban board, setting appropriate work in progress limits, combining Kanban and other agile methods, etc.) are still open. The aim of this paper is to upgrade previous research of different Kanban boards by proposing structure of a generic Kanban board and ground rules for its use, which could serve as a guiding reference for teams planning to introduce Scrumban as their development process. Additionally, an example of using such a board in practice is provided. The paper starts from the premise that appropriate combination of Scrum and Kanban advantages makes the most from both. Therefore, the proposed solution combines the most important Scrum practices (release and Sprint planning, regular delivery of increments, frequent feedback) with basic Kanban principles (visualization of workflow, limiting work in progress, change management). Key-Words: - Scrum, Kanban, agile methods, software development, software process management, quality improvement 1 Introduction According to the last State of Agile Development Numerous agile methods [1] have appeared in the Survey [9], the most widespread agile method is last fifteen years that – in contrast to traditional Scrum [10, 11].
    [Show full text]
  • Agile Software Development and Im- Plementation of Scrumban
    Joachim Grotenfelt Agile Software Development and Im- plementation of Scrumban Metropolia University of Applied Sciences Bachelor of Engineering Mobile Solutions Bachelor’s Thesis 30 May 2021 Abstrakt Författare Joachim Grotenfelt Titel Agile software utveckling och Implementation av Scrumban Antal Sidor 31 sidor Datum 30.05.2021 Grad Igenjör YH Utbildningsprogram Mobile Solutions Huvudämne Informations- och kommunikationsteknologi Instruktörer Mikael Lindblad, Projektledare Peter Hjort, Lektor Målet med avhandlingen var att studera agila metoder, hur de används i mjukvaruföretag och hur de påverkar arbetet i ett programvaruutvecklingsteam. Ett annat mål med avhandlingen var att studera bakgrunden till den agila metoden, hur den togs i bruk och hur den påverkar kundnöjdhet. I denna avhandling förklaras några existerande agila metoder, verktygen för hur agila metoder används, samt hur de påverkar programvaruutvecklingsteamet. Avhandlingen fokuserar sig på två agila metoder, Scrum och Kanban, eftersom de ofta används i olika företag. Ett av syftena med denna avhandling var att skapa förståelse för hur Scrumban metoden tas i bruk. Detta projekt granskar fördelarna med att ha ett mjukvaruutvecklingsteam som arbetar med agila processer. Projektet lyckades bra och en arbetsmiljö som använder agila metoder skapades. Fördelen blev att utvecklarteamet kunde göra förändringar när sådana behövdes. Nyckelord Agile, Scrum, Kanban, Scrumban Abstract Joachim Grotenfelt Author Basics of Agile Software Development and Implementation of Title Scrumban Number of Pages 31 pages Date 30.05.2021 Degree Bachelor of Engineering Degree Program Mobile Solutions Professional Major Information- and Communications Technology Instructors Mikael Lindblad, Project Manager Peter Hjort, Senior Lecturer The goal of the thesis is to study the Agile methods and how they affect the work of a soft- ware development team.
    [Show full text]
  • Agile Playbook V2.1—What’S New?
    AGILE P L AY B O OK TABLE OF CONTENTS INTRODUCTION ..........................................................................................................4 Who should use this playbook? ................................................................................6 How should you use this playbook? .........................................................................6 Agile Playbook v2.1—What’s new? ...........................................................................6 How and where can you contribute to this playbook?.............................................7 MEET YOUR GUIDES ...................................................................................................8 AN AGILE DELIVERY MODEL ....................................................................................10 GETTING STARTED.....................................................................................................12 THE PLAYS ...................................................................................................................14 Delivery ......................................................................................................................15 Play: Start with Scrum ...........................................................................................15 Play: Seeing success but need more fexibility? Move on to Scrumban ............17 Play: If you are ready to kick of the training wheels, try Kanban .......................18 Value ......................................................................................................................19
    [Show full text]
  • Appendix Project Management Appendix Project Management This Appendix Contains Additional Information on Project Management
    Appendix project management Appendix Project management This appendix contains additional information on project management. These are un edited versions of earlier more elaborate chapters on either traditional- and agile project management. Table of Contents Appendix Project management ...................................................................................................................... 1 1 Traditional project management ............................................................................................................. 2 1.1 Traditional project management theory and principles ................................................................... 2 1.2 Traditional project management the basics ..................................................................................... 3 2 Agile project management ...................................................................................................................... 5 2.1 Explaining agile project management ~ the agile manifesto ........................................................... 5 2.2 Typical agile mechanics, ideas and tools ~ agile in practice ........................................................... 7 2.2.1 Iterative development ~ iterative and incremental planning .................................................... 8 2.2.2 Communication, learning and visualisation ............................................................................. 9 2.2.3 Project results and project success ........................................................................................
    [Show full text]
  • AGILE PROJECT MANAGEMENT for TEAMS Anthony C
    AGILE PROJECT MANAGEMENT FOR TEAMS Anthony C. Mersino, PMP, PMI-ACP, CSM SM TWENTY-FIVE PROFESSIONAL DEVELOPMENT UNITS ©2016 Prodevia Learning, Inc. All Rights Reserved. The PMI R.E.P. logo is a mark of the Project Management Institute, Inc. This is a distance learning course that is self-paced and instructor supported. Be sure to review the section within this course guide entitled HOW TO COMPLETE THIS COURSE There you will find instructions to: Work through your course Formally complete it with Prodevia Learning Submit your professional development credits Welcome to Prodevia Learning Advanced Professional Development for Experienced Project Managers. Prodevia Learning offers advanced, expert-approved strategies for project managers to grow their skill sets and careers. We provide the most effective professional development courses in our industry written by the best names in our profession. You’ll discover how to interact much more successfully with your stakeholders and get the best outcomes from your projects than you ever thought possible. With Prodevia Learning courses, you can get started immediately because everything is available online as soon as you enroll. And, when you enroll in one of our paid classes, you’ll find they are also portable – you can optionally choose to have printed course guides shipped to you because we know you know that being chained to a computer or stuck at your office to take an online class is not always the most convenient method or the best way for you to grow and implement your learning. Your schedule requirements are ours, too. So, you have an unlimited amount of time to complete a course once you enroll.
    [Show full text]
  • Agile Project Management: Best Practices and Methodologies
    Agile Project Management: Best Practices and Methodologies WHITEPAPER Agile Project Management: Best Practices and Methodologies Agile Project Management: Best Practices and Methodologies 1. The Art of Project Management 2. Traditional Project Management Methodologies 3. Defining Agile Principles 4. Agile Methodologies 4.1 Scrum: roles, sprints and artifacts 4.2 Kanban: comprehensive solution to handling work in progress 4.3 Lean: eliminating waste in software engineering 5. Agile Software Engineering Best Practices: Extreme Programming Conclusion References 2 Agile Project Management: Best Practices and Methodologies 1. The Art of Project Management Regardless of industry, project management 1. Initiation has proven to be a crucial element of a 2. Planning company’s efficiency and its eventual success. 3. Execution In fact, projects are usually 2.5 times more 4. Performance/Monitoring successful when proven project management 5. Project close practices in place[1]. Used as a roadmap to accomplish specific tasks, As defined byGartner , project management these phases define the project management is “the application of knowledge, skills, tools lifecycle. and techniques to project activities to meet the project requirements”[2]. Being an integral part Yet, this structure is too general. A project of software engineering processes along with the usually has a number of internal stages within business analysis and requirement specification, each phase. They can vary greatly depending on design, programming and testing, the project the scope of work, the team, the industry and management has been a topic of considerable the project itself. debate for years. In attempts to find a universal approach to Regardless of the scope, any project should managing any project, humanity has developed follow a sequence of actions to be controlled a significant number of PM techniques and and managed.
    [Show full text]
  • Sample of the Scrumban
    CONTENTS Foreword by David J. Anderson xv Foreword by Jim Benson xix Preface xxiii Acknowledgments xxvii About the Author xxix Part I Introduction 1 Chapter 1 Manifestations: Scrumban Demystified 3 A Helpful Perspective 3 A Framework for [R]Evolution 4 Stop Drinking the Kool-Aid 8 Let’s Get Started 9 Part II Foundations—Starting with the End in Mind 11 Chapter 2 The Matrix and the Mess: Where It All Begins 13 Part 1: The Matrix (Scrumban’s Origins) 14 What Scrumban Is and What It Is Not 14 Managing Knowledge Work 16 Start the Journey with Systems Thinking 18 Scrumban Can Incorporate Other Models and Frameworks 20 Why Systems Thinking Is Relevant 20 Systems in Our Work Environments 25 Scrumban’s Approach to Understanding Systems 27 vii Reddy_CH00_FM.indd 7 6/9/15 9:35 AM viii Contents Part 2: The Mess (Reasons Scrumban Is Needed) 28 Why We Want to Be “Agile” 28 Why Agile Adoptions Stall or Fail 31 Tying It All Together 39 Chapter 3 The Mission: Clarifying the Relationship between Purpose, Values, and Performance 41 Why We’re Paid to Work 41 The Importance of Shared Purpose 42 The Importance of Adaptive Capabilities 43 Communication and Application of Core Values to Decision Making 45 Being Disciplined about the Right Metrics 49 Using Disciplined Approaches to Identify and Address the Most Important Problems 50 Tying It All Together 51 Chapter 4 Motivations: Why Scrumban Works 53 Where It All Began 53 Layering the Kanban Method 57 Attending to the Psychological Agenda 57 The Kanban Method’s Agendas 59 The Kanban Method’s Core Principles
    [Show full text]
  • Best Practices for Agile Adoption and Implementation
    AGILE ASSESSMENT GUIDE Best Practices for Agile Adoption and Implementation From September 28, 2020 to September 27, GAO-20-590G 2021, GAO is seeking input and feedback on this Exposure Draft from all interested September 2020 parties. See page 3 for more information. Contents Preface 1 Introduction 4 Chapter 1 Background 7 Chapter 2 Agile Adoption Challenges in the Federal Government and Actions Taken in Response 14 Chapter 3 Agile Adoption Best Practices 26 Team Dynamics and Activities 30 Best practice: Team composition supports Agile methods 30 Best practice: Work is prioritized to maximize value for the customer 35 Best practice: Repeatable processes are in place 40 Program Operations 44 Best practice: Staff are appropriately trained in Agile methods 44 Best practice: Technical environment enables Agile development 46 Best practice: Program controls are compatible with Agile 49 Organization Environment 51 Best practice: Organization activities support Agile methods 52 Best practice: Organization culture supports Agile methods 55 Best practice: Organization acquisition policies and procedures support Agile methods 61 Best Practices Checklist: Adoption of Agile Methods 63 Chapter 4 Overview of Agile Execution and Controls 65 Chapter 5 Requirements Development and Management in Agile 75 Elicit and Prioritize Requirements 80 Refine and Discover Requirements 83 Ensure Requirements are Sufficiently Complete, Feasible, and Verifiable for the Current State of the Program 84 Balance Customer Needs and Constraints 86 Test and Validate the System
    [Show full text]
  • Lean Software Development – What Exactly Are We Talking About?
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by University of Limerick Institutional Repository Lean Software Development – What Exactly Are We Talking About? Oisín Cawley1, Xiaofeng Wang2, Ita Richardson1, 1Lero-The Irish Software Engineering Research Centre, University of Limerick, Ireland. 2Free University of Bozen/Bolzano, ominikanerplatz 3 piazza Domenicani, I-39100 Bozen/Bolzano, Italy. 1{Oisin.Cawley, Ita.Richardson}@lero.ie, [email protected] Abstract. As the Software Engineering landscape continues to evolve and new paradigms are introduced, there can be a tendency for both industry and academia to enthusiastically embrace new approaches and march forward under whatever banner conventional wisdom has decided to adopt. One such banner is Lean Software Development, a paradigm that continues to see a growth in interest driven by the need for cost reductions within industry. The term lean attracts the attention of business, but precisely how it applies within software development is still being debated. In addition, its relationship to the better understood agile methodologies is also a topic for debate. Having been drawn into this research area ourselves, we present here a review of Lean Software Development and try to distil out for the reader some understanding of this somewhat undefined topic. We conclude with some thoughts on where this subject might go to from here. Keywords: Software Engineering, Software Development, Lean, Agile. 1 Introduction We are living in a period of history which is witnessing a drive for cost reductions and efficiencies across almost every business segment in almost every developed country. Traditionally businesses have been able to find efficiencies and cost reductions through automation and organisational restructuring of the more routine and repeatable processes.
    [Show full text]
  • Adopting Devops in Agile Challenges and Solutions
    Master of Science in Software Engineering February 2018 Adopting DevOps in Agile Challenges and Solutions Cheng Wang Changling Liu Faculty of Computing, Blekinge Institute of Technology, 371 79 Karlskrona, Sweden This thesis is submitted to the Faculty of Computing at Blekinge Institute of Technology in partial fulfilment of the requirements for the degree of Master of Science in Software Engineering. The thesis is equivalent to 20 weeks of full time studies. The authors declare that they are the sole authors of this thesis and that they have not used any sources other than those listed in the bibliography and identified as references. They further declare that they have not submitted this thesis at any other institution to obtain a degree. Contact Information: Author(s): Cheng Wang E-mail: [email protected] Changling Liu E-mail: [email protected] University advisor: Dr. Nauman Bin Ali Department of Software Engineering Faculty of Computing Internet : www.bth.se Blekinge Institute of Technology Phone : +46 455 38 50 00 SE–371 79 Karlskrona, Sweden Fax : +46 455 38 50 57 Abstract Background. DevOps is a hot topic in recent years. It emphasizes the combina- tion of development and operation. Agile is one of the most popular development methods, but Agile mainly focused on software development part, there is no more involvement in deployment and operations. In this case, many companies consider adopting DevOps in Agile to attempt to improve the situation. Objectives. The combination of two different technologies is bound to produce some challenges, whether it is for practitioners or researchers, it is very important to find these challenges and mitigate them, so this article aims to investigate the challenges of adopting DevOps in Agile, then through the systematic literature re- view and survey questionnaire to determine the corresponding mitigation strategy.
    [Show full text]
  • Disciplined Agile Delivery (DAD): the Foundation for Scaling Agile
    Disciplined Agile Delivery (DAD): The Foundation for Scaling Agile Scott W. Ambler Chief Methodologist for Agile and Lean, IBM Rational www.ibm.com/developerworks/blogs/page/ambler twitter.com/scottwambler © 2012 IBM Corporation We hope that you find these slides useful. If you would like to discuss this topic further, please contact IBM. 1 2 Agenda 1 Agile Fundamentals 2 Disciplined Agile Delivery (DAD) 3 Agility at Scale 4 Parting Thoughts 2 © 2012 IBM Corporation 2 What is agile? Agile is a highly collaborative, evolutionary, quality focused approach to software development. How agile is different: –Focus on collaboration –Focus on quality –Focus on working solutions –Agilists are generalizing specialists –Agile is based on practice, not theory 3 © 2012 IBM Corporation Focus on collaboration: Less paperwork and more conversation Stakeholders actively involved Focus on quality: Have a full regression test suite for your systems Develop loosely-coupled, highly cohesive architectures Refactor to keep them this way Focus on working solutions: Greater feedback makes agile projects easier to manage Less documentation is required Less bureaucracy Agilists are generalizing specialists: Fewer hand offs between people Fewer people required Specialists find it difficult at first to fit into the team Agile is based on practice, not theory: This is a significant change from traditional You need to see how agile works in practice to truly understand it 3 Why agile? Higher success rates Iterative Agile Lean Ad-Hoc Traditional 0% 20% 40% 60% 80% 100% Successful Challenged Failed Source: DDJ 2011 IT Project Success Survey 4 © 2012 IBM Corporation Detailed results online at www.ambysoft.com/surveys/ Success as defined by the respondent (this is the same for all slides in this deck).
    [Show full text]
  • Unblock! a Guide to the New Continuous Agile
    Last updated on: October 22, 2013 Version: 284 Copyright © 2013 by Assembla, Inc. All rights reserved. No part of this document may be reproduced in any form or by any electronic or mechanical means, including information storage and retrieval systems, without permission in writing from Assembla, Inc., except by a reviewer who may quote brief passages in a review. Assembla is a trademark of Assembla, Inc. All other trademarks are the property of their respective owners. Page 2/195 Unblock! A Guide to the New Continuous Agile Table Of Contents Introduction .................................................................................................................................... 5 The Big Trends ................................................................................................................................. 5 Welcome ......................................................................................................................................... 8 Trial by Fire .................................................................................................................................... 10 Continuous Agile .......................................................................................................................... 13 About Agile .................................................................................................................................... 13 Continuous Agile Principles .............................................................................................................
    [Show full text]