DOCSLIB.ORG

Dave's Agile Timeline—A Personal Journey Into Lean-Agile Thinking

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dave's Agile Timeline—A Personal Journey Into Lean-Agile Thinking DAVE’S AGILE TIMELINE—A PERSONAL JOURNEY INTO LEAN-AGILE THINKING 1987 - Work on Strategic Defense Initiative (Star Wars) 2006 - Begin deep-dive into Agile doctoral dissertation 2013 - Assist Federal Reserve Bank (FRB) with Agile testing 2018 - Develop business case for Lean-SAFe thinking 1987 - Work on NASA's $250M CASE Initiative (SSE) 2006 - Apply Agile principles to DoD virtual casefile system 2013 - Give keynote for FRB Agile transformation 2018 - Introduce Agile Datawarehousing and BI to Firm 1987 - Delve into Structured Analysis System Specification 2006 - Present first public Agile briefing in Hawaii 2013 - Assist FRB CIO with Agile business case 2018 - Develop Agile briefing on Harvard SAFe project 1987 - Delve into Hatley-Pirbhai Real-Time Specification 2007 - Scott Ambler assists with large-scale Agile survey 2013 - Assist GAO with Agile transformation 2018 - Develop CMMI to SAFe compliance map and checklist 1987 - Delve into Object Oriented Design (OOD) 2007 - Jeff Sutherland (Scrum) assists with dissertation 2013 - Become a Scaled Agile Framework (SAFe) Agilist 2018 - Collect multiple DevOps surveys and assessments 1988 - Meet OO design gurus, Grady Booch/Jean Ichbiah 2007 - Present findings of Agile survey at ALN-DC 2013 - Assist British graduate student with Agile thesis 2018 - Give Scaled Agile Framework (SAFe) Keynote to CMS 1989 - Work on NASA's Space Station Freedom (SSF) 2007 - Publish preliminary Agile survey results in UK 2013 - Give fourteen Agile talks in 2013 2018 - Give SAFe for Healthcare talk at Agile-Lean Summit 1989 - Design Prototype GUI for NASA's Space Station 2007 - Complete Agile dissertation and present results 2014 - Shift focus to Scaled Agile Framework (SAFe) 2018 - Give SAFe for Education talk to Virginia Tech 1989 - Take 240 hours of OO programming languages 2007 - Present Agile dissertation results in Hawaii 2015 - Begin focus on CI/CD/DevOps costs and benefits 2018 - Give SAFe tutorial to Quality Assurance Association 1990 - Start graduate work in Software Engineering 2008 - Mentor student on Agile Project Mgt dissertation 2014 - Give keynote to CRGT agile center of excellence 2018 - Help Firm capture $75 million SAFe contract 1990 - Study under OO software legend Charles McKay 2008 - Begin formal quantitative research into Agile ROI 2014 - Develop Agile CoQ principles for Quality Progress 2018 - Create a battery of Lean-Agile YouTube Videos 1990 - Work with NASA Space Shuttle Avionics Designers 2008 - Develop large database of Agile cost and benefit data 2014 - Publish lean project management book chapter 2018 - Help Firm win $200 million SAFe contract 1990 - Meet Shuttle designers Ted Keller and Kyle Rone 2008 - Develop agile cost and quality parametric models 2014 - Assist Capital One with Agile systems administration 2018 - Mentor student on Agile contracting dissertation 1990 - Take graduate courses from Shuttle legend Kyle Rone 2008 - Present findings of Agile ROI 2014 - Identify principles of DoD and government agility 2018 - Develop treatise on Agile contracting principles 1990 - Meet Code Inspection guru, Jeannie Clifton 2008 - Help ARC with Agile transformation 2014 - Give eleven Agile talks in 2014 2018 - Begin focus on Agile leadership principles 1991 - Exposed to Software-CMM Level 5 Shuttle team 2008 - Introduce Agile principles to DoD engineering dept. 2015 - Sharply focus to Scaled Agile Framework (SAFe) 2018 - Continue deep-dive into Business agility principles 1991 - Work in NASA Space Station Quality Assurance (QA) 2008 - Publish Agile ROI findings in UK 2015 - Convert ROI website to Agile website 2018 - Document case study on CMS-Medicaid SAFe rollout 1991 - Learn About Japanese Software Factories 2008 - Become a Certified Scrummaster 2015 - Give Agile tutorials to software radio contractor 2018 - Get second two Business Agility Certifications 1991 - Meet Capability Maturity Model guru, Watts Humphrey 2008 - Design/conduct university Agile capstone course 2015 - Give Agile tutorials to Contractor DoD program 2018 - Develop Agile DoD cloud computing principles 1991 - Meet software engineering legend, David Lorge Parnas 2008 - Serve as Product Owner/Scrummaster on 3 teams 2015 - Introduce SAFe to DoD systems engineering dept. 2018 - Give Agile in government lecture to Georgetown 1992 - Invited to Work on Lockheed's F-22 Avionics team 2008 - Publish history of Agile methods as book chapter 2015 - Focus on Agile systems engineering/embedded sys. 2018 - Give forty-two Agile talks in 2018 1992 - Meet OOA legends, Steven Mellor and Sally Shlaer 2008 - Assist $20 billion DoD IT program with Agile metrics 2015 - Assist U.S. Courts with SAFe Transformation 2019 - Introduce SAFe Acquisition practices to ODNI 1992 - Take OO coding from British legend Colin Atkinson 2008 - Begin deep-dive into XP release management 2015 - Give Agile talks to ballistic missile defense project 2019 - Continue Scaled Agile Framework (SAFe) deep-dive 1992 - Study IBM high-maturity SW-CMM Level 5 processes 2008 - Lead DoD Lean-agile enterprise initiative 2015 - Add focus on Agile performance measurement 2019 - Begin focus on Lean startup and Design sprints 1992 - Travel to Tokyo Japan to Tour Japanese Factories 2008 - Give four Agile talks in 2008 2015 - Develop Agile teamwork principles 2019 - Develop Lean-agile thinking leadership principles 1993 - Work in Japan's largest Japanese Software Factory 2009 - Publish Agile ROI textbook 2015 - Get first two Business Agility certifications 2019 - Collect state-of-the-art DevOps assessments 1994 - Tour Nippon Telephone & Telegraph's Software Factory 2009 - Help Contractor with DoD Agile transformation 2015 - Develop detailed AgileEVM tutorial 2019 - Develop library of lean, agile, and SAFe videos 1994 - Help Japanese become CMM Level 3/ISO 9001 Reg. 2009 - Mentor two students on agile-related dissertations 2015 - Design detailed model of Business agility principles 2019 - Begin deep-dive into Agile ALM tools and analytics 1995 - Modernize U.S. Air Force Static Radar Stealth Range 2009 - Present Agile education study at Agile 2009-Chicago 2015 - Give twenty-five Agile talks in 2015 2019 - Help large firm with its first SAFe rollout 1995 - Apply Shlaer/Mellor Object Oriented Analysis (OOA) 2009 - Give Agile ROI talk at Pentagon 2016 - Add focus on CI/CD/DevOps practices and ROI 2019 - Continue routine SAFe PI planning event rollouts 1995 - Study IBM high-maturity CMM Level 5 metrics/models 2009 - Learn of early Army software radio CI/CD case study 2016 - Add focus on Business Agility 2019 - Document careful case study on SAFe rollout 1996 - Develop advanced software inspection process models 2009 - Introduce CI/CD practices to DoD engineering dept. 2016 - Give first round of Business agility talks 2019 - Help Gov’t with a large-scale SAFe transformation 1996 - Work on Avionics manufacturing SW-CMM Initiative 2009 - Give sixteen Agile talks in 2009 2016 - Assist SSA with CI/CD/DevOps transformation 2019 - Become a Certified SAFe Release Train Engineer 1996 - Help DISA Contractor Become Software CMM Level 3 2010 - Begin focusing on Agile project management 2016 - Developing CI/CD/DevOps principles and practices 2019 - Develop Evolutionary Architecture/DevOps principles 1997 - Modernize 36 Military Logistics Depots w/rapid proto. 2010 - Adapt Don Reinertsen’s lean principles to APM/SAFe 2016 - Develop business case for CI/CD/DevOps practices 2019 - Give thirteen Lean, Agile, and DevOps talks in 2019 1997 - Conduct 10 Software CMM Level 3 Assessments 2010 - Begin exploring Agile project management scaling 2016 - Design Agile technology readiness assessment (TRA) 2020 - Become Certified SAFe 5.0 RTE, SA, SPC, AWS CCP 1997 - Support Navy Software Engineering Process Office 2010 - Introduce people to Scaled Agile Framework (SAFe) 2016 - Give joint IEEE/INCOSE SAFe tutorial 2020 - Develop new Lean, DevOps, and Design briefs/videos 1997 - Work on DISA's Global Combat Support System 2010 - Give Agile project mgt. Keynote in Helsinki, Finland 2016 - Develop Agile collaboration principles 2020 - Helped large public sector agency with SAFe rollout 1997 - Meet Victor Basili of NASA Software Engineering Lab 2010 - Publish Agile acquisition/systems engineering article 2016 - Mentor student on SAFe for hardware dissertation 2020 - Deliver multiple remote SAFe certification courses 1998 - Support DARPA Advanced Information Technology Sys 2010 - Successfully apply Scrum to BD proposal responses 2016 - Mentor student on Agile cost-benefit dissertation 2020 - Helped large U.S. DoD agency with SAFe rollout 1998 - Design U.S. Navy F-18 Software Budgeting System 2010 - Give seventeen Agile talks in 2010 2016 - Add Monte Carlo simulations to Agile ROI database 2020 - Develop new Business Agility ROI brief/business case 1998 - Identify Software Process Improvement Cost-Benefits 2011 - Begin focusing on Agile virtual teams 2016 - Apply Confidence intervals to Agile estimating 2020 - Mentor Silicon Valley Digital Transformation Startup 1998 - Deliver SPI Cost-Benefit Keynote to IBM Gaithersburg 2011 - Lead multi-billion DoD cloud project team (Scrum) 2016 - Give twenty Agile talks in 2016 2020 - Develop agile HR and product management workshops 1998 - Help IBM Gaithersburg become Software CMM Level 5 2011 - Become a PMI Agile Certified Practitioner (ACP) 2017 - Begin deep-dive into Scaled Agile Framework (SAFe) 2020 - Give sixteen Lean, Agile, and DevOps talks in 2020 1999 - Help GSA SDC become Software CMM Level 3 2011 - Study SAFe for APM, Acquisition, and Systems Eng. 2017
Load more

Recommended publications
  • Rugby - a Process Model for Continuous Software Engineering
    INSTITUT FUR¨ INFORMATIK DER TECHNISCHEN UNIVERSITAT¨ MUNCHEN¨ Forschungs- und Lehreinheit I Angewandte Softwaretechnik Rugby - A Process Model for Continuous Software Engineering Stephan Tobias Krusche Vollstandiger¨ Abdruck der von der Fakultat¨ fur¨ Informatik der Technischen Universitat¨ Munchen¨ zur Erlangung des akademischen Grades eines Doktors der Naturwissenschaften (Dr. rer. nat.) genehmigten Dissertation. Vorsitzender: Univ.-Prof. Dr. Helmut Seidl Prufer¨ der Dissertation: 1. Univ.-Prof. Bernd Brugge,¨ Ph.D. 2. Prof. Dr. Jurgen¨ Borstler,¨ Blekinge Institute of Technology, Karlskrona, Schweden Die Dissertation wurde am 28.01.2016 bei der Technischen Universitat¨ Munchen¨ eingereicht und durch die Fakultat¨ fur¨ Informatik am 29.02.2016 angenommen. Abstract Software is developed in increasingly dynamic environments. Organizations need the capability to deal with uncertainty and to react to unexpected changes in require- ments and technologies. Agile methods already improve the flexibility towards changes and with the emergence of continuous delivery, regular feedback loops have become possible. The abilities to maintain high code quality through reviews, to regularly re- lease software, and to collect and prioritize user feedback, are necessary for con- tinuous software engineering. However, there exists no uniform process model that handles the increasing number of reviews, releases and feedback reports. In this dissertation, we describe Rugby, a process model for continuous software en- gineering that is based on a meta model, which treats development activities as parallel workflows and which allows tailoring, customization and extension. Rugby includes a change model and treats changes as events that activate workflows. It integrates re- view management, release management, and feedback management as workflows. As a consequence, Rugby handles the increasing number of reviews, releases and feedback and at the same time decreases their size and effort.
    [Show full text]
  • Safe® 5.0 Glossary Scaled Agile Framework Terms and Definitions English
    SAFe® 5.0 Glossary Scaled Agile Framework Terms and Definitions English PROVIDED BY www.scaledagileframework.com | www.scaledagile.com © Scaled Agile, Inc. Welcome to the SAFe® Glossary Make the Most of Your Learning Access the SAFe Community Platform Mange your member profile, access videos and training resources, join Communities of Practice, and more. Prepare Yourself Access your learning plan featuring your digital workbook, study materials, and certification practice test Become a Certified SAFe Professional Get certified to validate your knowledge, expand your professional capabilities, and open the door to new career opportunities. Access SAFe Content and Tools Access professional development resources and your trainer enablement plan to teach SAFe instructor-led courses. Collaborate in real time with your team and others Choose from ready-made templates to easily set up events like PI Planning and retrospectives—all with SAFe Collaborate. Showcase SAFe Credentials Display your digital badge to promote your SAFe capabilities and proficiencies throughout your career. community.scaledagile.com Guide to acronyms and abbreviations APD Agile Product Delivery OKR Objective and Key Results ART Agile Release Train OpEx Operating Expenses BO Business Owner PDCA Plan, Do, Check, Adjust BV Business Value PI Program Increment BVIR Big Visual Information Radiator PM Product Management CapEx Capital Expenses PO/PM Product Owner/Product Manager CD Continuous Deployment PO Product Owner CE Continuous Exploration ROAM Resolved, Owned, Accepted,
    [Show full text]
  • Case Study BMC12
    With guidance from Rally, BMC made a variety of changes to the organization to ensure success of their agile process. How BMC is Scaling Agile Development www.rallydev.com www.rallydev.com www.rallydev.com www.rallydev.com www.rallydev.com www.rallydev.com A Rally Customer Experience Report Something Ventured, Something Gained Designating an Agile Evangelist Scaling Agile Practices Across a Large Organization Creating a Highly Responsive Development Organization Requirements Runway, continued Despite a myriad of challenges and lessons learned, BMC This position was responsible for coordinating the training and rollout process; helping to resolve issues and facilitate Becky Strauss describes the concept like this: feels the end result is well worth the effort. The most The final measure any development process is in how it delivers value to customers. The move to Agile enables BMC to telling measure of their success is that the organization can communications. She also acted as ScrumMaster for the In BMC’s first year of agile development, they rolled out As you enter the Houston headquarters of “The benefits of Agile are multi-dimensional. create products in a way that is much more responsive to changing customer needs. Israel Gat summarizes it like this: not imagine going back to their old way of developing software. “scrum of scrums” as the need to coordinate multiple, agile processes and tools to over 300 people. Along the “The idea of a requirements runway is to plan ahead just enough to keep the project BMC Software and proceed across a peaceful, But the most important change is that it way, they learned some key lessons about successfully moving as fast as possible, without investing too much time and effort elaborating zen-like courtyard, you notice something that Agile is at BMC to stay.
    [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]
  • Software Architecture: the Next Step for Object Technology (PANEL)
    Software Architecture: The Next Step for Object Technology (PANEL) Bruce Anderson, University of ESSPX (moderator) Mary Shaw, Carnegie-Mellon University Larry Best, American Management Systems Kent Beck, First Class Software What is the next step for you? Progress comes Abstract from taking aware steps, but what steps are those? Architectures are the structuring paradigms, styles They could be in attempting to discover and and patterns that make up our software systems. catalogue architectures; creating awareness of this They are important in many ways: they allow us to level of product envisioning; doing design more talk usefully about systems without talking about consciously; finding ways of describing systems; their detail; a knowledge of them gives us design consolidating legacy code; abandoning legacy code; choices; attention to this level can make systems and making new software lifecycles. families of systems have the non-functional What is the next step for the community? Are there properties we want, especially changeability. ways to work that go beyond projects and Each panelist will address the following issues: companies? Will there be focus on the community, l What is architecture? which suggests cooperation, learning, divergence l What is the value you have had so far from and empowerment; or on the marketplace, which this concept? suggests competition, confidentiality, convergence l What is the next step for you? and dependence? l What is the next step for the community? 2 Mary Shaw 1 Background Software architecture is concerned with the What is architecture? We all have experience of organization of software systems: the selection of systems of great conceptual clarity and integrity.
    [Show full text]
  • The Legacy of Victor R. Basili
    University of Tennessee, Knoxville TRACE: Tennessee Research and Creative Exchange About Harlan D. Mills Science Alliance 2005 Foundations of Empirical Software Engineering: The Legacy of Victor R. Basili Barry Boehm Hans Dieter Rombach Marvin V. Zelkowitz Follow this and additional works at: https://trace.tennessee.edu/utk_harlanabout Part of the Physical Sciences and Mathematics Commons Recommended Citation Boehm, Barry; Rombach, Hans Dieter; and Zelkowitz, Marvin V., "Foundations of Empirical Software Engineering: The Legacy of Victor R. Basili" (2005). About Harlan D. Mills. https://trace.tennessee.edu/utk_harlanabout/3 This Book is brought to you for free and open access by the Science Alliance at TRACE: Tennessee Research and Creative Exchange. It has been accepted for inclusion in About Harlan D. Mills by an authorized administrator of TRACE: Tennessee Research and Creative Exchange. For more information, please contact [email protected]. University of Tennessee, Knoxville Trace: Tennessee Research and Creative Exchange The Harlan D. Mills Collection Science Alliance 1-1-2005 Foundations of Empirical Software Engineering: The Legacy of Victor R.Basili Barry Boehm Hans Dieter Rombach Marvin V. Zelkowitz Recommended Citation Boehm, Barry; Rombach, Hans Dieter; and Zelkowitz, Marvin V., "Foundations of Empirical Software Engineering: The Legacy of Victor R.Basili" (2005). The Harlan D. Mills Collection. http://trace.tennessee.edu/utk_harlan/36 This Book is brought to you for free and open access by the Science Alliance at Trace: Tennessee Research and Creative Exchange. It has been accepted for inclusion in The Harlan D. Mills Collection by an authorized administrator of Trace: Tennessee Research and Creative Exchange. For more information, please contact [email protected].
    [Show full text]
  • The Great Methodologies Debate: Part 1
    ACCESS TO THE EXPERTS The Journal of Information Technology Management December 2001 Vol. 14, No. 12 The Great Methodologies Debate: Part 1 Resolved “Today, a new debate rages: agile software Traditional methodologists development versus rigorous software are a bunch of process- development.” dependent stick-in-the-muds who’d rather produce flawless Jim Highsmith, Guest Editor documentation than a working system that meets business needs. Opening Statement Jim Highsmith 2 Rebuttal Lightweight, er, “agile” Agile Can Scale: Inventing and Reinventing methodologists are a bunch of SCRUM in Five Companies glorified hackers who are going to be in for a heck of a surprise Jeff Sutherland 5 when they try to scale up their “toys” into enterprise-level software. Agile Versus Traditional: Make Love, Not War! Robert L. Glass 12 Business Intelligence Methodologies: Agile with Rigor? Larissa T. Moss 19 Agility with the RUP Philippe Kruchten 27 Extreme Requirements Engineering Larry Wagner 34 Exclusion, Assumptions, and Misinterpretation: Foes of Collaboration Lou Russell 39 Opening Statement by Jim Highsmith In the early 1980s, I participated in rigorous software development. others be able to understand the one round of methodology debate. Agile approaches (Extreme similarities and differences and be Structured analysis and design Programming, Crystal Methods, able to apply the right mix to their champions such as Tom DeMarco, Lean Development, Feature-Driven own organization. Both the SEI and Ed Yourdon, and Tim Lister were Development, Adaptive Software Rational have made wonderful on one side of the debate, while Development, SCRUM, and contributions to software develop- data-driven design aficionados like Dynamic Systems Development ment, but it is important to Ken Orr, Jean-Dominique Warnier, Methodology) populate one camp.
    [Show full text]
  • Watts S. Humphrey (1927-2010)
    1 Watts S. Humppyhrey (1927-2010) Five lessons I learned from an inspiring leader Daniel M. Roy September 2011 PSP, TSP, Personal Software Process and Team Software Process are service marks of CMU CMM and Capability Maturity Model are registered in the U.S. patent and trademark office Myers-Briggs Type Indicator and MBTI are registered trademarks trademarks of Consulting Psychologists Press, Inc. Copyright © 2011 STPP, Inc. (Software Technology, Process & People) 2 My Watts connection Project leader at SEI 1990-1995 Cer tified th e F rench t ransl ati on of CMM material in 1993 Took the first PSP class at CMU from Watts in the winter of 1994 Copyright © 2011 STPP, Inc. (Software Technology, Process & People) 3 From CMM to PSP “My first class was a blessing in a way that I hdhad not expecte d. Three peop le from th e SEI were taking the course: Dan Roy, Julia MllMullaney (h(then Ju lia G a le) , and dJ Jim O ver. Subsequently, they all decided to work with me iiiihPSPilin transitioning the PSP intro general practice. They have been doing so ever si”ince.” Three process perspectives, WSH, 2001 Copyright © 2011 STPP, Inc. (Software Technology, Process & People) 4 My Watts connection Project leader at SEI 1990-1995 Cer tified th e F rench t ransl ati on of CMM material in 1993 Took the first PSP class at CMU from Watts in the winter of 1994 STPP created in May 1995 on his advice Invited Watts to Paris in October1995 Became SEI transition partner in 1997 Copyright © 2011 STPP, Inc.
    [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]
  • SCALED AGILE @ SYSTEMS ENGINEERING How Two Seemingly Different Approaches to Solving a Problem Create Synergies in R&D and Increase Efficiency
    SCALED AGILE @ SYSTEMS ENGINEERING How two seemingly different approaches to solving a problem create synergies in R&D and increase efficiency. SCALED AGILE @ SYSTEMS ENGINEERING I September 2020 Content 01 Introduction 6 02 What Do We Mean by Agility? 8 03 What Do We Mean by Systems Engineering? 10 04 The Synthesis, or: The Best of Both Worlds 14 INNOVATION 05 The Agile Systems Engineering Transformation 24 06 Outlook 28 FLEXIBILITY REACTION EFFECTIVENESS ADAPTIVITY 2 3 SCALED AGILE @ SYSTEMS ENGINEERING I September 2020 01 Introduction Agility and systems engineering are an integral part of employee motivation, R&D currently favors two models – sys- We know the theory and roles – how does the (lower sickness rates, higher employer attractiveness and lower responsive, flexible product development. tems engineering (SE) or the Scaled Agile Framework (SAFe®). practical implementation work? turnover), was not included due to inconsistent measurement Both models have their own strengths, but also reveal areas How can our processes and tools be tailored to SE methods used by the companies, but is a positive side effect. In recent decades, the business world has been character- that have not yet been taken into account and where further or agile methods? The following three main topics are distinguished for the ized by volatility, uncertainty, complexity and ambiguity – or potential can be tapped. Synchronization with organization – how do we implementation of the approach and will be described in more “VUCA,” as the concept is known for short. Driven by climate solve the link to other areas? detail later in the white paper. change and the ongoing pandemic, this has recently been The aim of this white paper is to present the profitable aspects Agility has only worked in software so far – how can supplemented by an additional acronym – “BANI,” which of both models in a joint synthesis and thus present a systems we scale the model? 1) Use of agile and systems engineering methods at stands for brittle, anxious, nonlinear and incomprehensible.
    [Show full text]
  • Safe® 4.6 Glossary Scaled Agile Framework Terms and Defnitions English
    SAFe® 4.6 Glossary Scaled Agile Framework Terms and Defnitions English PROVIDED BY www.scaledagileframework.com | www.scaledagile.com © Scaled Agile, Inc. Welcome to the SAFe® Glossary Make the Most of Your Learning SAFe Access the SAFe Community Platform Manage your member profle, join communities of practice, and access the member directory Prepare Yourself Prepare for certifcation with your learning plan: access your course workbook, study materials, and practice test prior to taking your certifcation exam Get Certifed SAFe Get certifed to achieve recognition of your skills and open the door to new career opportunities Showcase SAFe Certifcations Use your digital badge to view global job insights, track market labor data, and see where your skills are in demand community.scaledagile.com Guide to acronyms and abbreviations ART Agile Release Train PDCA Plan, Do, Check, Adjust BO Business Owner PI Program Increment BV Business Value PM Product Management BVIR Big Visual Information Radiator PO/PM Product Owner / Product Manager CapEx Capital Expenses PO Product Owner CD Continuous Delivery ROAM Resolved, Owned, Accepted, Mitigated CE Continuous Exploration RR Risk Reduction CI Continuous Integration RTE Release Train Engineer CFD Cumulative Flow Diagram S4T SAFe® for Teams CoD Cost of Delay SAFe® Scaled Agile Framework CoP Community of Practice SA SAFe® Agilist DoD Defnition of Done SBD Set-Based Design DSU Daily Stand-up SM Scrum Master EA Enterprise Architect SMART Specifc, Measurable, Achievable, EO Epic Owner Realistic, Time-bound
    [Show full text]
  • The Role of Empirical Study in Software Engineering
    The Role of Empirical Study in Software Engineering Victor R. Basili Professor, University of Maryland and Director, Fraunhofer Center - Maryland © 2004 Experimental Software Engineering Group, University of Maryland Outline • Empirical Studies – Motivation – Specific Methods – Example: SEL • Applications – CeBASE – NASA High Dependability Computing Project – The Future Combat Systems Project – DoE High Productivity Computing System 2 Motivation for Empirical Software Engineering Understanding a discipline involves building models, e.g., application domain, problem solving processes And checking our understanding is correct, e.g., testing our models, experimenting in the real world Analyzing the results involves learning, the encapsulation of knowledge and the ability to change or refine our models over time The understanding of a discipline evolves over time This is the empirical paradigm that has been used in many fields, e.g., physics, medicine, manufacturing Like other disciplines, software engineering requires an empirical paradigm 3 Motivation for Empirical Software Engineering Empirical software engineering requires the scientific use of quantitative and qualitative data to understand and improve the software product, software development process and software management It requires real world laboratories Research needs laboratories to observe & manipulate the variables - they only exist where developers build software systems Development needs to understand how to build systems better - research can provide models to help Research
    [Show full text]