DOCSLIB.ORG

The Speed to Cool

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Speed to Cool Agile Methods in Minutes Craig Smith Welcome… Let’s Go! Foundations Manifesto for -- Agile Software Development Manifesto for -- Agile Software Development Values Signatories 17 signatories 2001 agilemanifesto.org Principles 1 Scrum 1 Scrum “A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.” Process Basis for most iterative processes / methods currently in use. Opinion Roles + Theory - Jeff Sutherland / Ken Schwaber 1996 scrumguides.org 1a Scrumbut (Scrumand) 1a ScrumBut (ScrumAnd) “We're doing Scrum but...” “We use Scrum and...” ScrumBut vs ScrumAnd ScrumAnd framework ScrumBut "We're doing Scrum but..." our sprints are 12 weeks long” ScrumAnd “We use Scrum and we are collaborating and brainstorming within the Scrum Team to increase value every Sprint.” Eric Gunnerson 2006 blogs.msdn.com/b/ericgu/archive/2006/10/13/scrumbut.aspx Ken Schwaber 2008 kenschwaber.wordpress.com/2012/04/05/scrum-but-replaced-by-scrum-and/ 2 Extreme Programming (XP) 2 Extreme Programming (XP) “Extreme Programming is the first popular methodology to view software development as an exercise in coding rather than an exercise in management.” Practices Process Principles + Practices have become Values - software engineering good practice Opinion Kent Beck 1996 extremeprogramming.org 3 Crystal 3 Crystal “Crystal is a family of human-powered, adaptive, ultralight, “stretch-to-fit” software development methodologies… designed to scale by project size and criticality” Exploratory 360 degree Early victory Walking skeleton Incremental rearchitecture Information radiators Methodology: Strategies Size vs Criticality Properties + - Alistair Cockburn 1992 alistair.cockburn.us/crystal+methodologies Dynamic Systems Development Method 4 (DSDM) Dynamic Systems Development Method 4 (DSDM) “Incorporates project management disciplines… to ensure… project benefits are clear,… proposed solution is feasible and …solid foundations in place…” Process MoSCoW Practice Deliverables + Principles - DSDM Consortium 1994 dsdm.org Feature Driven Development 5 (FDD) Feature Driven Development 5 (FDD) “a recipe for simplified, enhanced and measurable project management: patterns of play that bring success.” Process Parking Lot Practice Best Practices + - Jeff De Luca 1997 featuredrivendevelopment.com/ Adaptive Software Development 6 (ASD) Adaptive Software Development (ASD) / 6 Adaptive Leadership “Adaptive Software Development does not provide a set of prescriptive rules or tasks, but a framework of concepts, practices, and guidelines” Complex Adaptive Systems (CAS) Theory Agents Environments Lifecycle Emergence + Characteristics - Jim Highsmith 1992 adaptivesd.com Lean Lean / Lean Manufacturing / Lean 7 Enterprise / Toyota Production System Lean / Lean Manufacturing / Lean 7 Enterprise / Toyota Production System “Lean uses less of everything compared with mass production… As it inevitably spreads… will change almost everything in almost every industry…” Improvement Kata Lean Principles + 8 Wastes (Muda) - Eli Whitney Taichi Ono James Womack 1850 1936 1990 lean.org 7a Lean Software Development 7a Lean Software Development “Lean uses less of everything compared with mass production… As it inevitably spreads… will change almost everything in almost every industry…” 7 Principles / 22 Tools + - Mary & Tom Poppendieck 2003 poppendieck.com Deming System of 8 Profound Knowledge Deming System of 8 Profound Knowledge “An effective theory of management that provides a framework of thought and action for any leader wishing to transform and create a thriving organization…” Systems Thinking Knowledge of Variation Theory of Knowledge + 14 points W. Edwards Deming 1939 deming.org for management - 9 (Product Development) Flow 9 (Product Development) Flow “...the dominant paradigm for managing product development is wrong. Not just a little wrong, but wrong to its very core.” High Delay Cost Job First Optimum Batch Size 175 Principles Failure to correctly quantify economics + Blindness to queues Worship of efficiency Hostility to variability Worship of conformance Institutionalization of large batch sizes Underutilization of cadence Managing timelines instead of queues Absence of WIP constraints Inflexibility Noneconomic flow control 12 Cardinal Centralized control Sins - Donald G. Reinertsen 2009 lpd2.com / leanproductflow.com Kanban 10 (Modern Management Methods) Kanban 10 (Modern Management Methods) “...evolutionary change model that utilizes a kanban (small k) pull system, visualization, and other tools to catalyze the introduction of Lean ideas into technology…” Start with what you do now Agree to pursue incremental, evolutionary change Respect the current process, roles, responsibilities and titles Leadership at all levels 4 Principles Kanban Board 5 Core + Properties - David J. Anderson 2010 djaa.com 11 Personal Kanban 11 Personal Kanban “...provides a light, actionable, achievable framework for understanding our work and its context.” Get your stuff ready Establish your value stream Establish your backlog Establish your work in progress limit Begin to pull Reflect 5 Steps 2 Rules of Personal Kanban + Throughput - Jim Benson / Tonianne DeMaria Barry 2011 personalkanban.com 12 Lean Startup 12 Lean Startup “It's ultimately an answer to the question ‘How can we learn more quickly what works, and discard what doesn't?” 5 Principles Process + - Eric Ries 2008 theleanstartup.com Popularised Extensions Hybrid Agile (Scrumban, Xanpan, 13 Nonban, Water-Scrum-Fall) Hybrid Agile (Scrumban, Xanpan, 13 Nonban, Water-Scrum-Fall) “Using one or more aspects of different methods Xanban Scrumban Nonban Water Scrum Fall ScrumPLOP 14 (Pattern Languages of Programs) ScrumPLOP 14 (Pattern Languages of Programs) “ScrumPLoP mission is to build a body of pattern literature around… communities, describing… insights, so we can easily share them.” Pattern Spreadsheet Pattern Map + - Jeff Sutherland / Jim Coplien 2010 scrumplop.org Enterprise Transition Framework 15 (ETF) Enterprise Transition Framework 15 (ETF) “…focus of ETF is to allow an organization to implement continuous improvement and to experience change in an empirically controlled way.” + - Framework Agile42 2014 agile42.com/en/agile-transition/etf/ 16 Software Faster 16 Software Faster “…Brings agile principles into the 21st century… to think differently about design, architecture, development & testing, operations, automation & team dynamics…” 3 ages of agile Patterns Workshop Agenda Deliberate Discovery Avoiding problems Fits in my head Micro services Focussed effort Release mentality is harmful Software: asset or liability Blink estimation - + Dan North 2010 dannorth.net Extreme Manufacturing (XM) 17 (Wikispeed) Extreme Manufacturing (XM) 17 (Wikispeed) “…Set of technical practices and management principles to go from an idea to a product or service in the customers hands in less than 7 days.” Wikispeed + Process - Joe Justice 2008 wikispeed.org Certifications 18 (BABOK / PMI ACP / icAgile / …) Certifications 18 (BABOK / PMI ACP / icAgile / …) PMI-ACP PRINCE2 Agile Best Practice IIBA BABOK Agile Extension ICAgile Certification Scale Agile Unified Process 19 (AUP) Agile Unified Process 19 (AUP) “…A simplified version of the Rational Unified Process (RUP)…” Lifecycle Philosophies Scott Ambler 2005 ambysoft.com/unifiedprocess/agileUP.html Disciplined Agile Delivery 19a (DAD) Disciplined Agile Delivery 19a (DAD) “…People-first, learning-oriented hybrid agile approach… has a risk-value lifecycle, is goal-driven, is scalable, and is enterprise aware.” Lifecycle Scaling Key Aspects + - Scott Ambler 2012 disciplinedagiledelivery.com Enterprise Unified Process 19b (EUP) Enterprise Unified Process 19b (EUP) “…a full-fledged software process …is an extension to the solution delivery methodologies such as DAD.” Lifecycle + - When to Adopt Scott Ambler 1999 enterpriseunifiedprocess.com Large Scale Scrum 20 (LeSS) Large Scale Scrum 20 (LeSS) “…a label to imply regular Scrum plus the set of tips we have seen work in large multiteam, multisite and offshore agile development.” + LeSS (up to 8 teams) - LeSS Huge (up to a few thousand people) Craig Larman / Bas Vodde 2008 2015 less.works/ 21 Enterprise Scrum 21 Enterprise Scrum “… provide an expanded and more detailed framework foundation of Scrum so that we can use Scrum for business, generic or scalable purposes.” Model Improvement Cycles Business Skin + - Mike Beedle 2010 enterprisescrum.com Scaled Agile Framework 22 (SaFE) Scaled Agile Framework 22 (SaFE) “…Interactive knowledge base for implementing agile practices at enterprise scale... Highlights the individual roles, teams, activities & artifacts necessary to scale agile…” + - Framework Dean Leffingwell 2007 scaledagileframework.com 23 @Spotify / Squadification 23 @Spotify / Squadification “…Scaling using tribes, squads, chapters and guilds” Engineering Approach Culture Principles + - Henrik Kniberg / Spotify 2012 labs.spotify.com 24 Nexus Framework 24 Nexus Framework “…a framework consisting of roles, events, artifacts, and techniques that bind and weave together the work of approximately three to nine Scrum Teams…” Builds on existing Scrum knowledge 3-9 Teams Core Features Nexus Integration Team Builds on Scrum + Integrated Increment Adds “Nexus” to the ceremonies - Framework Ken Schwaber 2015 scrum.org/nexus Development & Testing 25 DevOps 25 DevOps “a response to the interdependence of software development and IT operations.” Process Lifecycle Relationship
Load more

Recommended publications
  • Critical Success Factors for Agile Project Management in Non- Software Related Product Development Teams
    Western Michigan University ScholarWorks at WMU Dissertations Graduate College 12-2017 Critical Success Factors for Agile Project Management in Non- Software Related Product Development Teams Jeff Totten Western Michigan University, [email protected] Follow this and additional works at: https://scholarworks.wmich.edu/dissertations Part of the Curriculum and Instruction Commons, Educational Assessment, Evaluation, and Research Commons, and the Instructional Media Design Commons Recommended Citation Totten, Jeff, "Critical Success Factors for Agile Project Management in Non-Software Related Product Development Teams" (2017). Dissertations. 3178. https://scholarworks.wmich.edu/dissertations/3178 This Dissertation-Open Access is brought to you for free and open access by the Graduate College at ScholarWorks at WMU. It has been accepted for inclusion in Dissertations by an authorized administrator of ScholarWorks at WMU. For more information, please contact [email protected]. CRITICAL SUCCESS FACTORS FOR AGILE PROJECT MANAGEMENT IN NON-SOFTWARE RELATED PRODUCT DEVELOPMENT TEAMS by Jeff Totten A dissertation submitted to the Graduate College in partial fulfillment of the requirements for the degree of Doctor of Philosophy Educational Leadership, Research, and Technology Western Michigan University December 2017 Doctoral Committee: Louann Bierlein Palmer, Ed.D., Chair David Szabla, Ed.D. Daniel Gaymer, Ph.D. CRITICAL SUCCESS FACTORS FOR AGILE PROJECT MANAGEMENT IN NON-SOFTWARE RELATED PRODUCT DEVELOPMENT TEAMS Jeff Totten, Ph.D. Western Michigan University, 2017 The use of agile project management methods in the software development industry is well established and researched. The purpose of this study is to understand whether agile project management methods (Scrum in particular) used successfully in the software industry are also being used in full, or in part, in non-software development industries when managing product development projects.
    [Show full text]
  • Joe Justice on Agile Manufacturing Learning Consortium Webinar Q&A
    Joe Justice on Agile Manufacturing Learning Consortium Webinar Q&A October 21, 2105 1. How do you deal with certification cycles of federal authorities such as the FDA, FCC, etc., in the context of an Agile manufacturing approach? I would highly recommend the Scrum Inc. webinar “Agile Testing” to take you through the best we’ve seen so far. http://www.scruminc.com/scrumlab-prime/ 2. XMfg - How different is it from the factory model followed in batch jobs production in the manufacturing industry? XMfg practices reduce the cost to make change to the line and the product. This can support batch jobs or one-piece continuous flow. The fastest manufacturing method we’ve seen so far is massively parallel concurrent manufacturing, which funnels work more like a current- generation hyper-threading CPU than a traditional line flow such as batch jobs or one-piece continuous flow. And ultimately XMfg allows the company to affordably iterate more towards this pattern each sprint, again by lowering the cost (in time and money) to make change. 3. Can this be applicable for a nonprofit, high-scale contemporary art exhibition (50-plus projects, two years)? If there is a clear vision (which is encouraged to evolve, but clear at any given point in time), these approaches will apply. And I’d love to see it; please email [email protected] if you try it! If you would like help getting started, I’ll invite you to attend a Certified ScrumMaster class: http://www.scruminc.com/scrum-training/scrum-courses-list/ 4. How long did it take to "print" the carbon car you witnessed at the trade show? Cincinnati BAAM completed the Local Motors DDM (direct digital manufacturing) porotype car during the two-day exhibition.
    [Show full text]
  • Extreme Programming from Wikipedia, the Free Encyclopedia
    Create account Log in Article Talk Read Edit View history Search Extreme programming From Wikipedia, the free encyclopedia Main page Extreme programming (XP) is a software development methodology which is Contents intended to improve software quality and responsiveness to changing customer Featured content requirements. As a type of agile software development,[1][2][3] it advocates frequent Current events "releases" in short development cycles, which is intended to improve productivity Random article and introduce checkpoints at which new customer requirements can be adopted. Donate to Wikipedia Wikipedia store Other elements of extreme programming include: programming in pairs or doing Interaction extensive code review, unit testing of all code, avoiding programming of features Help until they are actually needed, a flat management structure, simplicity and clarity in About Wikipedia code, expecting changes in the customer's requirements as time passes and the Community portal problem is better understood, and frequent communication with the customer and Recent changes among programmers.[2][3][4] The methodology takes its name from the idea that the Contact page Planning and feedback loops in beneficial elements of traditional software engineering practices are taken to extreme programming. Tools "extreme" levels. As an example, code reviews are considered a beneficial What links here practice; taken to the extreme, code can be reviewed continuously, i.e. the practice Related changes Software development of pair programming. Upload file process Special pages Critics have noted several potential drawbacks,[5] including problems with Core activities Permanent link unstable requirements, no documented compromises of user conflicts, and a Requirements · Design · Construction · Testing · Debugging · Deployment · Page information lack of an overall design specification or document.
    [Show full text]
  • AGILE @ HARDWARE MANUFACTURING Smash Your Time-To-Market, Boost Innovative Potential and Change the Game in Your Industry with These Innovative Methods and Practices
    AGILE @ HARDWARE MANUFACTURING Smash your time-to-market, boost innovative potential and change the game in your industry with these innovative methods and practices. A GLADWELL ACADEMY & BLINKLANE CONSULTING WHITE PAPER T: +31 (0)20 24 022 44 | E: [email protected] gladwellacademy.com CONTENTS WHY BRING AGILE IDEAS TO HARDWARE DEVELOPMENT? Why bring Agile ideas to hardware development? 3 The advantages of working Agile have been a revolution for the world of software Why not? 5 development - and following that, for much of the business world in general. From services firms to municipal governments, the promise of Agile ideas is irresistibly convincing. Agile methodology for the hardware environment 6 � The ability to ‘turn on a dime, for a dime’. Product-centered and process-centered approaches 8 � The ability to drastically reduce time-to-market. � The increased sense of empowerment that pervades all layers of the organization, so even the humblest coder feels like they might improve the entire company - Case studies 12 given a valuable enough insight. � The ability to improve client collaboration during development, by effectively The course ‘Agile for Hardware’ 16 responding to new insights and changing requirements. � The earnest commitment to customer value, rather than to internal goals and priorities. ‘Certified Hardware Agilist’ 18 � The substantial elimination of waste from the equation. About the authors 19 THE DIFFERENCE DISAPPEARS The proliferation of Agile ways of working beyond software developers goes hand in hand with the increased popularity of software development itself, though. More and more organizations are building in-house software development departments to support the increased digitalization of their services.
    [Show full text]
  • Scrum for Hardware, with Joe Justice of WIKISPEED and Scrum Inc, USA
    ! Podcast Episode #10 – How to think like Elon Musk – Scrum for Hardware, with Joe Justice of WIKISPEED and Scrum Inc, USA RAW TRANSCRIPT OF INTERVIEW Balint: Today I have a special guest. If there was a black belt in his field, he would certainly be one of its holders. He's a master of a type of project management, an in- novation method - Agile. Specifically, he's into Scrum, which is the most commonly used Agile method. My guest is Joe Justice from the US, president of Scrum Inc. Hardware at Scrum Inc., and founder of a company called Team WIKISPEED, which is still very much alive. Welcome, Joe, to this episode. Joe: Balint, thanks so much for having me on your Hardware Entrepreneur Podcast. I'm excited to be a part of it and share the best of what I’m learning with your audi- ence. Balint: I'm very excited to talk to you now and share this knowledge because I think you have very valuable points to make which I would try to bring out. We’ve met a few times when you visited Zurich where you regularly give some courses and talks on Scrum through your involvement at Scrum Inc. I've been impressed by your en- thusiasm and, of course, also by your results, every time I hear you give a talk or also a webinar, which I attended today, on Scrum in automotive. I'm equally impressed also whenever I read about Scrum method published by your colleague Jeff Suther- land who is the CEO of Scrum Inc.
    [Show full text]
  • Agile Transformation from Agile Experiments to Operating Model Transformation: How Do You Compare to Others?
    Agile Transformation From Agile experiments to operating model transformation: How do you compare to others? 2019 Survey on Agility 2 Preface Preface What comes to mind when you think of Agile? Driven by leadership ambition to remain relevant in the digital future, we see in both our Global CEO Outlook 2019 and our Harvey Nash/KPMG CIO Survey 2019 that Agile is Do you think of IT? Realising results fast? Developing software? increasingly a strategic priority towards becoming future ready. In this survey, we would Or do you think broader? like to dive into this topic further and involve the target operating model on how Agile can ― Working as a team? be implemented. ― Working with multiple self-organising teams? ― Collaborating with customers? We see that we live in a diverse world – our survey shows Agile maturity is different from ― Integrating business and IT? country to country. Originally a European survey, we concluded the survey with responses from more than 120 participants from 17 countries, which include: There is no single answer. Originally defined in 2001 in the Agile Manifesto as a reaction to ― Argentina ― Denmark ― Poland the slow, bureaucratic and stifled creativity experienced in traditional waterfall methods of ― Austria ― France ― Singapore software development, Agile formed the basis for a revolution in the way software is ― Belgium ― Germany ― Sweden developed. ― Bolivia ― Hong Kong SAR ― The Netherlands ― Brazil ― Italy ― Turkey Nowadays we see this revolution increasing its footprint as principles to define entire ― Czech Republic ― Norway organisations and is vastly outgrowing the development of software on a team level. Digitisation is driving the need for flexibility and the increased role of technology in We hope you enjoy our survey; that it contributes to your insights on how to apply agility delivering value.
    [Show full text]
  • Agile Methodologies in Product Development Case: Discrete Manufacturing and Assembly
    AGILE METHODOLOGIES IN PRODUCT DEVELOPMENT CASE: DISCRETE MANUFACTURING AND ASSEMBLY Master's thesis Visamäki, Strategic Leading of Technology-based Business Spring 2019 Tero Lappalainen ABSTRACT Strategic Leading of Technology-based Business Visamäki Author Tero Lappalainen Year 2019 Title Agile Methodologies in Product Development Case: Discrete Manufacturing and Assembly Supervisor(s) Jukka Pulkkinen ABSTRACT During last years, the most successful ICT companies has adopted Agile methodologies. What happens when these methods are used in totally different industry? Rapid product development cycles and managing continuously changing priorities are key attributes in developing highly customized products. Aim of this action research was to understand, whether Discrete Manufacturing and Assembly Company's product development process required changes, could design work benefit from agile practices, how new operation model can be implemented and what kind of results it will deliver. Qualitative semi-structured interviews were used to understand current situation and requirement for change. In parallel, a literature and media study were made of methodologies with highest adoption and growth, and industry specific applications. Based on this information, a framework comparison according subject’s prerequisites and a recommendation of most suitable frameworks was made. This was followed by a new operating model description, implementation of required tools and introduction of new model. After and before surveys and comparison of design release volumes for past two years was conducted to evaluate the change impact. Based on the results, a following conclusion was made. Using agile methodology and practices led into increased process clarity, better support for design of high-quality products and increased transparency and communication perceived by process contributors.
    [Show full text]