DOCSLIB.ORG

The Art of Agile Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Art of Agile Development The Art of Agile Development The Art of Agile Development James Shore and Shane Warden Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo The Art of Agile Development by James Shore and Shane Warden Copyright © 2008 James Shore and chromatic. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mary O’Brien Indexer: Joe Wizda Production Editor: Sarah Schneider Cover Designer: Karen Montgomery Copyeditor: Sarah Schneider Interior Designer: David Futato Proofreader: Sada Preisch Illustrator: Robert Romano Printing History: October 2007: First Edition. The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. The Theory in Practice series designations, The Art of Agile Development, and related trade dress are trademarks of O’Reilly Media, Inc. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. TM This book uses RepKover™, a durable and flexible lay-flat binding. ISBN: 978-0-596-52767-9 [C] [1/10] 1263253177 To our families. Table of Contents .........................................................................Preface . xxiii Part I. Getting Started 1. Why Agile? . .................................................................. 3 Understanding Success 3 Beyond Deadlines 4 The Importance of Organizational Success 5 Enter Agility 6 Organizational Success 6 Technical Success 7 Personal Success 7 2. How to Be Agile . ............................................................. 9 Agile Methods 9 Don’t Make Your Own Method 9 The Road to Mastery 11 Find a Mentor 12 3. Understanding XP . ........................................................ 15 The XP Lifecycle 17 How It Works 19 Our Story Continues 22 The XP Team 28 The Whole Team 28 On-Site Customers 29 Programmers 33 Testers 34 Coaches 35 Other Team Members 36 The Project Community 36 Filling Roles 39 Team Size 39 IX Full-Time Team Members 40 XP Concepts 40 Refactoring 41 Technical Debt 41 Timeboxing 41 The Last Responsible Moment 42 Stories 42 Iterations 42 Velocity 43 Theory of Constraints 43 Mindfulness 43 4. Adopting XP . ............................................................... 45 Is XP Right for Us? 45 Prerequisite #1: Management Support 46 Prerequisite #2: Team Agreement 46 Prerequisite #3: A Colocated Team 47 Prerequisite #4: On-Site Customers 47 Prerequisite #5: The Right Team Size 49 Prerequisite #6: Use All the Practices 50 Recommendation #1: A Brand-New Codebase 51 Recommendation #2: Strong Design Skills 51 Recommendation #3: A Language That’s Easy to Refactor 52 Recommendation #4: An Experienced Programmer-Coach 52 Recommendation #5: A Friendly and Cohesive Team 53 Go! 53 The Challenge of Change 55 Final Preparation 56 Applying XP to a Brand-New Project (Recommended) 57 Applying XP to an Existing Project 59 Applying XP in a Phase-Based Organization 62 Extremities: Applying Bits and Pieces of XP 64 Assess Your Agility 65 Self-Assessment Quiz 67 Part II. Practicing XP 5.................................................................... Thinking . 73 Pair Programming 74 Why Pair? 75 How to Pair 75 Driving and Navigating 76 Pairing Stations 77 Challenges 78 Questions 79 Results 81 Contraindications 81 X TABLE OF CONTENTS Alternatives 81 Further Reading 82 Energized Work 82 How to Be Energized 82 Supporting Energized Work 83 Taking Breaks 84 Questions 84 Results 85 Contraindications 85 Alternatives 86 Further Reading 86 Informative Workspace 86 Subtle Cues 87 Big Visible Charts 87 Hand-Drawn Charts 88 Process Improvement Charts 88 Gaming 89 Questions 90 Results 90 Contraindications 90 Alternatives 90 Further Reading 91 Root-Cause Analysis 91 How to Find the Root Cause 91 How to Fix the Root Cause 92 When Not to Fix the Root Cause 92 Questions 92 Results 93 Contraindications 93 Alternatives 93 Retrospectives 94 Types of Retrospectives 94 How to Conduct an Iteration Retrospective 94 Step 1: The Prime Directive 95 Step 2: Brainstorming 95 Step 3: Mute Mapping 96 Step 4: Retrospective Objective 97 After the Retrospective 97 Questions 98 Results 99 Contraindications 100 Alternatives 100 Further Reading 100 6. Collaborating . ............................................................ 101 Trust 103 Team Strategy #1: Customer-Programmer Empathy 103 Team Strategy #2: Programmer-Tester Empathy 104 Team Strategy #3: Eat Together 104 TABLE OF CONTENTS XI Team Strategy #4: Team Continuity 105 Impressions 105 Organizational Strategy #1: Show Some Hustle 106 Organizational Strategy #2: Deliver on Commitments 106 Organizational Strategy #3: Manage Problems 107 Organizational Strategy #4: Respect Customer Goals 108 Organizational Strategy #5: Promote the Team 109 Organizational Strategy #6: Be Honest 109 Questions 111 Results 112 Contraindications 112 Alternatives 112 Further Reading 113 Sit Together 113 Accommodating Poor Communication 113 A Better Way 114 Exploiting Great Communication 114 Secrets of Sitting Together 115 Making Room 116 Designing Your Workspace 116 Sample Workspaces 117 Adopting an Open Workspace 118 Questions 119 Results 120 Contraindications 120 Alternatives 120 Further Reading 121 Real Customer Involvement 121 Personal Development 122 In-House Custom Development 122 Outsourced Custom Development 123 Vertical-Market Software 123 Horizontal-Market Software 124 Questions 124 Results 124 Contraindications 125 Alternatives 125 Ubiquitous Language 125 The Domain Expertise Conundrum 125 Two Languages 126 How to Speak the Same Language 126 Ubiquitous Language in Code 127 Refining the Ubiquitous Language 128 Questions 129 Results 129 Contraindications 129 Alternatives 129 Further Reading 130 Stand-Up Meetings 130 XII TABLE OF CONTENTS How to Hold a Daily Stand-Up Meeting 130 Be Brief 131 Questions 132 Results 132 Contraindications 133 Alternatives 133 Further Reading 133 Coding Standards 133 Beyond Formatting 134 How to Create a Coding Standard 134 Dealing with Disagreement 136 Adhering to the Standard 136 Questions 137 Results 138 Contraindications 138 Alternatives 138 Iteration Demo 138 How to Conduct an Iteration Demo 139 Two Key Questions 140 Weekly Deployment Is Essential 141 Questions 142 Results 143 Contraindications 143 Alternatives 143 Reporting 143 Types of Reports 144 Progress Reports to Provide 144 Progress Reports to Consider 145 Management Reports to Consider 145 Reports to Avoid 148 Questions 149 Results 150 Contraindications 151 Alternatives 151 Further Reading 151 7.................................................................. Releasing . 153 “Done Done” 155 Production-Ready Software 156 How to Be “Done Done” 157 Making Time 157 Questions 158 Results 159 Contraindications 159 Alternatives 159 No Bugs 159 How Is This Possible? 160 How to Achieve Nearly Zero Bugs 161 Ingredient #1: Write Fewer Bugs 161 TABLE OF CONTENTS XIII Ingredient #2: Eliminate Bug Breeding Grounds 162 Ingredient #3: Fix Bugs Now 162 Ingredient #4: Test Your Process 164 Ingredient #5: Fix Your Process 165 Invert Your Expectations 166 Questions 166 Results 168 Contraindications 168 Alternatives 168 Further Reading 169 Version Control 169 Concurrent Editing 170 Time Travel 171 Whole Project 171 Customers and Version Control 172 Keep It Clean 173 Single Codebase 174 Appropriate Uses of Branches 174 Questions 174 Results 176 Contraindications 176 Alternatives 176 Further Reading 177 Ten-Minute Build 177 Automate Your Build 178 How to Automate 178 When to Automate 179 Automating Legacy Projects 179 Ten Minutes or Less 180 Questions 181 Results 182 Contraindications 182 Alternatives 183 Continuous Integration 183 Why It Works 183 How to Practice Continuous Integration 184 Never Break the Build 184 The Continuous Integration Script 185 Introducing Continuous Integration 186 Dealing with Slow Builds 187 Multistage Integration Builds 187 Questions 188 Results 190 Contraindications 190 Alternatives 191 Collective Code Ownership 191 Making Collective Ownership Work 192 Working with Unfamiliar Code 192 Hidden Benefits 193 XIV TABLE OF CONTENTS Questions 193 Results 194 Contraindications 194 Alternatives 195 Documentation 195 Work-In-Progress Documentation 195 Product Documentation 196 Handoff Documentation 196 Questions 197 Results 197 Contraindications 197 Alternatives 198 8................................................................... Planning . 201 Vision 202 Product Vision 202 Where Visions Come From 203 Identifying the Vision 203 Documenting the Vision 204 How to Create a Vision Statement 204 Promoting the Vision 205 Questions 206 Results 207 Contraindications 207 Alternatives 207 Further Reading 207 Release Planning 207 One Project at a Time 207 Release Early, Release Often 208 How to Release Frequently 210 An Example 211 Adapt Your Plans 212 Keep Your Options Open 213 How to Create a Release Plan 214 Planning at the Last Responsible Moment 216 Adaptive Planning and Organizational Culture 218 Questions 219 Results 219 Contraindications 220 Alternatives 220 Further Reading 221 The Planning Game 221 How to Play 221 How to Win 223 Questions 224 Results 225 Contraindications 225 Alternatives 225
Load more

Recommended publications
  • Global SCRUM GATHERING® Berlin 2014
    Global SCRUM GATHERING Berlin 2014 SESSION DESCRIPTION TABLE OF CONTENTS SESSION TIMETABLE Monday, September 22nd – AM Sessions WELCOME & OPENING KEYNOTE - 9:00 – 10:30 Welcome Remarks ROOM Dave Sharrock & Marion Eickmann Opening Keynote Potsdam I/III Enabling the organization as a complex eco-system Dave Snowden AM BREAK – 10:30 – 11:00 90 MINUTE SESSIONS - 11:00 – 12:30 SESSION & SPEAKER TRACK LEVEL ROOM Managing Agility: Effectively Coaching Agile Teams Bring Down the Performing Tegel Andrea Tomasini, Bent Myllerup Wall Temenos – Build Trust in Yourself, Your Team, Successful Scrum Your Organization Practices: Berlin Norming Bellevue Christine Neidhardt, Olaf Lewitz Never Sleeps A Curious Mindset: basic coaching skills for Managing Agility: managers and other aliens Bring Down the Norming Charlottenburg II Deborah Hartmann Preuss, Steve Holyer Wall Building Creative Teams: Ideas, Motivation and Innovating beyond Retrospectives Core Scrum: The Performing Charlottenburg I Cara Turner Bohemian Bear Scrum Principles: Building Metaphors for Retrospectives Changing the Forming Tiergarted I/II Helen Meek, Mark Summers Status Quo Scrum Principles: My Agile Suitcase Changing the Forming Charlottenburg III Martin Heider Status Quo Game, Set, Match: Playing Games to accelerate Thinking Outside Agile Teams Forming Kopenick I/II the box Robert Misch Innovating beyond Let's Invent the Future of Agile! Core Scrum: The Performing Postdam III Nigel Baker Bohemian Bear Monday, September 22nd – PM Sessions LUNCH – 12:30 – 13:30 90 MINUTE SESSIONS - 13:30
    [Show full text]
  • Enabling Devops on Premise Or Cloud with Jenkins
    Enabling DevOps on Premise or Cloud with Jenkins Sam Rostam [email protected] Cloud & Enterprise Integration Consultant/Trainer Certified SOA & Cloud Architect Certified Big Data Professional MSc @SFU & PhD Studies – Partial @UBC Topics The Context - Digital Transformation An Agile IT Framework What DevOps bring to Teams? - Disrupting Software Development - Improved Quality, shorten cycles - highly responsive for the business needs What is CI /CD ? Simple Scenario with Jenkins Advanced Jenkins : Plug-ins , APIs & Pipelines Toolchain concept Q/A Digital Transformation – Modernization As stated by a As established enterprises in all industries begin to evolve themselves into the successful Digital Organizations of the future they need to begin with the realization that the road to becoming a Digital Business goes through their IT functions. However, many of these incumbents are saddled with IT that has organizational structures, management models, operational processes, workforces and systems that were built to solve “turn of the century” problems of the past. Many analysts and industry experts have recognized the need for a new model to manage IT in their Businesses and have proposed approaches to understand and manage a hybrid IT environment that includes slower legacy applications and infrastructure in combination with today’s rapidly evolving Digital-first, mobile- first and analytics-enabled applications. http://www.ntti3.com/wp-content/uploads/Agile-IT-v1.3.pdf Digital Transformation requires building an ecosystem • Digital transformation is a strategic approach to IT that treats IT infrastructure and data as a potential product for customers. • Digital transformation requires shifting perspectives and by looking at new ways to use data and data sources and looking at new ways to engage with customers.
    [Show full text]
  • Integrating the GNU Debugger with Cycle Accurate Models a Case Study Using a Verilator Systemc Model of the Openrisc 1000
    Integrating the GNU Debugger with Cycle Accurate Models A Case Study using a Verilator SystemC Model of the OpenRISC 1000 Jeremy Bennett Embecosm Application Note 7. Issue 1 Published March 2009 Legal Notice This work is licensed under the Creative Commons Attribution 2.0 UK: England & Wales License. To view a copy of this license, visit http://creativecommons.org/licenses/by/2.0/uk/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. This license means you are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must give the original author, Jeremy Bennett of Embecosm (www.embecosm.com), credit; • For any reuse or distribution, you must make clear to others the license terms of this work; • Any of these conditions can be waived if you get permission from the copyright holder, Embecosm; and • Nothing in this license impairs or restricts the author's moral rights. The software for the SystemC cycle accurate model written by Embecosm and used in this document is licensed under the GNU General Public License (GNU General Public License). For detailed licensing information see the file COPYING in the source code. Embecosm is the business name of Embecosm Limited, a private limited company registered in England and Wales. Registration number 6577021. ii Copyright © 2009 Embecosm Limited Table of Contents 1. Introduction ................................................................................................................ 1 1.1. Why Use Cycle Accurate Modeling .................................................................... 1 1.2. Target Audience ................................................................................................ 1 1.3. Open Source ..................................................................................................... 2 1.4. Further Sources of Information ......................................................................... 2 1.4.1.
    [Show full text]
  • Code Profilers Choosing a Tool for Analyzing Performance
    Code Profilers Choosing a Tool for Analyzing Performance Freescale Semiconductor Author, Rick Grehan Document Number: CODEPROFILERWP Rev. 0 11/2005 A profiler is a development tool that lets you look inside your application to see how each component—each routine, each block, sometimes each line and even each instruction—performs. You can find and correct your application’s bottlenecks. How do they work this magic? CONTENTS 1. Passive Profilers ...............................................3 6. Comparing Passive and Active 1.1 How It Is Done—PC Sampling ................4 Profilers .................................................................9 1.2 It Is Statistical ................................................4 6.1 Passive Profilers—Advantages ...............9 6.2 Passive Profilers—Disadvantages .........9 2. Active Profilers ...................................................4 6.3 Active Profilers—Advantages ................10 2.1 Methods of Instrumentation .....................5 6.4 Active Profilers—Disadvantages ..........11 3. Source Code Instrumentation ...................5 7. Conclusion .........................................................12 3.1 Instrumenting by Hand ..............................5 8. Addendum: Recursion and 4. Object Code Instrumentation ....................5 Hierarchies ........................................................12 4.1 Direct Modification .......................................6 4.2 Indirect Modification ...................................7 5. Object Instrumentation vs. Source Instrumentation
    [Show full text]
  • Debugging and Profiling with Arm Tools
    Debugging and Profiling with Arm Tools [email protected] • Ryan Hulguin © 2018 Arm Limited • 4/21/2018 Agenda • Introduction to Arm Tools • Remote Client Setup • Debugging with Arm DDT • Other Debugging Tools • Break • Examples with DDT • Lunch • Profiling with Arm MAP • Examples with MAP • Obtaining Support 2 © 2018 Arm Limited Introduction to Arm HPC Tools © 2018 Arm Limited Arm Forge An interoperable toolkit for debugging and profiling • The de-facto standard for HPC development • Available on the vast majority of the Top500 machines in the world • Fully supported by Arm on x86, IBM Power, Nvidia GPUs and Arm v8-A. Commercially supported by Arm • State-of-the art debugging and profiling capabilities • Powerful and in-depth error detection mechanisms (including memory debugging) • Sampling-based profiler to identify and understand bottlenecks Fully Scalable • Available at any scale (from serial to petaflopic applications) Easy to use by everyone • Unique capabilities to simplify remote interactive sessions • Innovative approach to present quintessential information to users Very user-friendly 4 © 2018 Arm Limited Arm Performance Reports Characterize and understand the performance of HPC application runs Gathers a rich set of data • Analyses metrics around CPU, memory, IO, hardware counters, etc. • Possibility for users to add their own metrics Commercially supported by Arm • Build a culture of application performance & efficiency awareness Accurate and astute • Analyses data and reports the information that matters to users insight • Provides simple guidance to help improve workloads’ efficiency • Adds value to typical users’ workflows • Define application behaviour and performance expectations Relevant advice • Integrate outputs to various systems for validation (e.g.
    [Show full text]
  • Ready to Innovate?
    ReadyThe Visual COBOL 5.0to Azure innovate? DevOps and Serverless Computing Walkthrough June 2019 The Visual COBOL 5.0 Azure DevOps and Serverless Computing Walkthrough 2 Visual COBOL 5.0— blue sky thinking Ready to build your Cloud story? This is primarily a how-to technical guide that enables COBOL and non- COBOL developers to modernize legacy applications using the Cloud— it’s all about bridging the old with the new. New to Visual COBOL? This is your guided tour of everything it can do towards modernizing core COBOL applications. Already on board? This is the update that explains how to take your applications beyond the next level and on to the Cloud. What will you learn? Much of this Guide focuses on the technical, practical aspect of creating next-gen apps from COBOL code. Among other new skills, you will discover how to… • Bring a COBOL application into Visual Studio or Eclipse • Edit, compile and debug COBOL applications using the IDE • Modernize COBOL apps using .NET and C# • Create and deploy a COBOL microservice as a Serverless application in the Cloud • Build, test and publish your application via a DevOps pipeline • Understand the latest native Cloud technologies The Visual COBOL 5.0 Azure DevOps and Serverless Computing Walkthrough 3 What’s new in Visual COBOL 5.0? This latest update of our unrivalled development experience significantly extends Visual COBOL’s capabilities. It brings the Cloud closer, enabling access to DevOps and Serverless computing for COBOL systems. For Micro Focus, Visual COBOL 5.0 is where meet our customers’ need for application modernization using the Cloud.
    [Show full text]
  • Bugs and Debugging
    CS50 Bugs and Debugging Overview Key Terms A bug is an error in code which results in a program either failing, or exhibiting a be- • bugs havior that is different from what the programmer expects. Bugs can be frustrating to • debugging deal with, but every programmer encounters them. Debugging is the process of trying • debugger to identify and fix bugs that exist in code. Programmers will often do this by making use of a program called a debugger, which assists in the debugging process. • breakpoint • debug50 Debugging Basics Programs generally perform computations much faster than a human possibly could, which makes it difficult to see what's wrong with a program just by running it all the way through. Debuggers are valuable because they allow a programmer to freeze a program at a particular line, known as a breakpoint, so that the programmer can see what's happening at that point in time. It also allows the programmer to execute the program one line at a time, so that the programmer can follow along with every decision that a program makes. Using debug50 debug50 is a program that we've created that runs a built-in graphical debugger in the CS50 IDE. Before you run debug50, you must set at least one breakpoint. If you have a general sense for where your program seems to be going wrong, it may be wise to set a breakpoint a few lines before there, so that you can see what's happening in your program as it moves into the section that you believe is causing the problem.
    [Show full text]
  • Software Debugging Techniques
    Software debugging techniques P. Adragna Queen Mary, University of London Abstract This lecture provides an introduction to debugging, a crucial activity in ev- ery developer's life. After an elementary discussion of some useful debugging concepts, the lecture goes on with a detailed review of general debugging tech- niques, independent of any specific software. The final part of the lecture is dedicated to analysing problems related to the use of C++ , the main program- ming language commonly employed in particle physics nowadays. Introduction According to a popular definition [1], debugging is a methodical process of finding and reducing the number of bugs, or defects, in a computer program. However, most people involved in spotting and removing those defects would define it as an art rather then a method. All bugs stem from a one basic premise: something thought to be right, was in fact wrong. Due to this simple principle, truly bizarre bugs can defy logic, making debugging software challenging. The typical behaviour of many inexperienced programmers is to freeze when unexpected problems arise. Without a definite process to follow, solving problems seems impossible to them. The most obvious reaction to such a situation is to make some random changes to the code, hoping that it will start working again. The issue is simple: the programmers have no idea of how to approach debugging [2]. This lecture is an attempt to review some techniques and tools to assist non-experienced pro- grammers in debugging. It contains both tips to solve problems and suggestions to prevent bugs from manifesting themselves. Finding a bug is a process of confirming what is working until something wrong is found.
    [Show full text]
  • The Design of a Debugger Unit for a RISC Processor Core
    Rochester Institute of Technology RIT Scholar Works Theses 3-2018 The Design of a Debugger Unit for a RISC Processor Core Nikhil Velguenkar [email protected] Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Velguenkar, Nikhil, "The Design of a Debugger Unit for a RISC Processor Core" (2018). Thesis. Rochester Institute of Technology. Accessed from This Master's Project is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. The Design of a Debugger Unit for a RISC Processor Core by Nikhil Velguenkar Graduate Paper Submitted in partial fulfillment of the requirements for the degree of Master of Science in Electrical Engineering Approved by: Mr. Mark A. Indovina, Lecturer Graduate Research Advisor, Department of Electrical and Microelectronic Engineering Dr. Sohail A. Dianat, Professor Department Head, Department of Electrical and Microelectronic Engineering Department of Electrical and Microelectronic Engineering Kate Gleason College of Engineering Rochester Institute of Technology Rochester, New York March 2018 To my family and friends, for all of their endless love, support, and encouragement throughout my career at Rochester Institute of Technology Abstract Recently, there has been a significant increase in design complexity for Embedded Sys- tems often referred to as Hardware Software Co-Design. Complexity in design is due to both hardware and firmware closely coupled together in-order to achieve features forlow power, high performance and low area. Due to these demands, embedded systems consist of multiple interconnected hardware IPs with complex firmware algorithms running on the device.
    [Show full text]
  • Global SCRUM GATHERING® Berlin 2014
    Global SCRUM GATHERING Berlin 2014 SESSION DESCRIPTION TABLE OF CONTENTS SESSION TIMETABLE Monday, September 22nd – AM Sessions WELCOME & OPENING KEYNOTE - 9:00 – 10:30 Welcome Remarks ROOM Dave Sharrock & Marion Eickmann Opening Keynote Potsdam I/III Enabling the organization as a complex eco-system Dave Snowden AM BREAK – 10:30 – 11:00 90 MINUTE SESSIONS - 11:00 – 12:30 SESSION & SPEAKER TRACK LEVEL ROOM Managing Agility: Effectively Coaching Agile Teams Bring Down the Performing Tegel Andrea Tomasini, Bent Myllerup Wall Temenos – Build Trust in Yourself, Your Team, Successful Scrum Your Organisation Practices: Berlin Norming Bellevue Christine Neidhardt, Olaf Lewitz Never Sleeps A Curious Mindset: basic coaching skills for Managing Agility: managers and other aliens Bring Down the Norming Charlottenburg II Deborah Hartmann Preuss, Steve Holyer Wall Building Creative Teams: Ideas, Motivation and Innovating beyond Retrospectives Core Scrum: The Performing Charlottenburg I Cara Turner Bohemian Bear Scrum Principles: Building Metaphors for Retrospectives Changing the Forming Tiergarted I/II Helen Meek, Mark Summers Status Quo Scrum Principles: My Agile Suitcase Changing the Forming Charlottenburg III Martin Heider Status Quo Game, Set, Match: Playing Games to accelerate Thinking Outside Agile Teams Forming Kopenick I/II the box Robert Misch Innovating beyond Let's Invent the Future of Agile! Core Scrum: The Performing Postdam III Nigel Baker Bohemian Bear Monday, September 22nd – PM Sessions LUNCH – 12:30 – 13:30 90 MINUTE SESSIONS - 13:30
    [Show full text]
  • Software Debugging Using the Debugger SAM4E Xplained Pro
    Faculty of Technology and Society Computer Engineering Bachelor’s thesis 15 credits Software debugging using the debugger SAM4E Xplained Pro Mjukvarufelsökning med användning av felsökningsverktyget SAM4E Xplained Pro Hamoud Abdullah Nadia Manoh Exam: Bachelor of Science in Engineering Examiner: Ulrik Ekedahl Area: Computer Engineering Supervisor: Magnus Krampell Date of final seminar: 2018-08-21 Abstract Embedded systems are found in almost every device used in our daily lives, including cell phones, refrigerators, and cars. Some devices may be significantly more sensitive than others, meaning a bug appearing in a system could cause harm, even loss of human lives or cause no harm at all. To reduce bugs in a system, software testing and software debugging are performed. The Computer Science program at Malmö University does not focus on teaching software debugging using a debugger. Thus, this thesis presents a debugging lab created for Computer Science students, considered to help them gain knowledge in how to use the debugger SAM4E Xplained Pro to locate bugs. As a result, four students performed the debugging lab of which 75 percent of the bugs were found and remedied. Keywords: embedded system, software testing, software debugging, software failure, software bugs debugging techniques Sammanfattning Inbyggda system finns i nästan alla enheter som används i vårt dagliga liv, som exempelvis mobiltelefoner, kylskåp och bilar. En del enheter kan vara betydligt känsligare än andra, vilket innebär att en bugg som existerar i ett system kan orsaka skada, till och med förlust av människoliv, eller orsakar ingen skada alls. Mjukvarutestning och mjukvarufelsökning genomförs för att reducera buggar i ett system.
    [Show full text]
  • Software Testing Strategies and Methods CONTENTS
    Software Engineering Software Testing Strategies and Methods CONTENTS I. Software Testing Fundamentals 1. Definition of Software Testing II. Characteristics of Testing Strategies III. Software Verification and Validation (V&V) IV. Testing Strategies 1. Unit Testing 2. Integration Testing V. Alpha and Beta Testing ( Concept and differences) VI. System Testing 1. Concept of System Testing VII. Concept of White-box and Black-Box Testing VIII. Debugging 1. Concept and need of Debugging 2. Characteristics of bugs IX. Debugging Strategies 1. Concept of Brute Force, Back Tracking, Induction, Deduction Anuradha Bhatia Software Engineering I. Software Testing Fundamentals 1. Definition of Software Testing i. Software testing is a method of assessing the functionality of a software program. ii. There are many different types of software testing but the two main categories are dynamic testing and static testing. II. Characteristics of Testing Strategies Figure 1: Software Testing Software Testing Myths and Facts: Just as every field has its myths, so does the field of Software Testing. Software testing myths have arisen primarily due to the following: i. Lack of authoritative facts. ii. Evolving nature of the industry. iii. General flaws in human logic. Some of the myths are explained below, along with their related facts: 1. MYTH: Quality Control = Testing. FACT: Testing is just one component of software quality control. Quality Control includes other activities such as Reviews. Anuradha Bhatia Software Engineering 2. MYTH: The objective of Testing is to ensure a 100% defect- free product. FACT: The objective of testing is to uncover as many defects as possible. Identifying all defects and getting rid of them is impossible.
    [Show full text]