1. CMMI and Scrum TWO BRANCHES OF SOFTWARE DEVELOPMENT
|
|
- Jessie Snow
- 8 years ago
- Views:
Transcription
1 1. CMMI and Scrum TWO BRANCHES OF SOFTWARE DEVELOPMENT
2 Enterprise Software Engineering Agenda 1. CMMI and Scrum 2. Kanban Software Engineering 3. Software Development Life Cycle 4. Secure Software Engineering 2
3 Enterprise Software Engineering Agenda 1. CMMI and Scrum 2. Kanban Software Engineering 3. Software Development Life Cycle 4. Secure Software Engineering 3
4 What is Software Engineering? Software engineering is the application of a systematic, disciplined, quantifiable approach to the design, development, operation, and maintenance of software, and the study of these approaches; that is, the application of engineering to software From cradle to grave
5 The Three Critical Dimensions 5
6 What is Software Engineering?
7 SWEBOK V3 (on Review Stage) Knowledge Areas (KAs) Software requirements Software design Software construction Software testing Software maintenance Software configuration management Software engineering management Software engineering process Software engineering models and methods Software quality Software engineering professional practice Software engineering economics Computing foundations Mathematical foundations Engineering foundations Software security specialized knowledge area 15 Knowledge Areas
8 Growing Pains
9
10 10
11 Crafting Software Resource Input Code Debug Test Product 11
12 Engineering Software Resource Input F R PM D C RA T Product 12
13 Build a Bridge vs. Build Software Design 10% Construction 90% Design 90% Construction 10% 13
14 Software Engineering Maturity Stages of engineering maturity Professional Engineering Commercial Practice SW Engineering Craftsmanship Currently, software engineering might be placed some where between craftsmanship and commercial practice 14
15 Waterfall
16 The Waterfall Process Requirements Design Code Testing Requirements Design Code Testing DONE Requirements Design Code Testing Requirements Design Code Testing Requirements Design Code Testing Requirements Design Code Testing Time
17 Gimme all requirements, or.
18 The Waterfall Process Big Requirements Up Front (BRUF) System Requirements Software Requirements Analysis But Program Design Coding V&V Operations
19 The Waterfall Process Big Requirements Up Front (BRUF) System Requirements Software Requirements Specification Preliminary Design Document Software Requirements Prelim. Review UI Design Document Preliminary Design Preliminary Design Final Design Analysis Design Review Analysis Program Design Program Design V&V Plan Coding Coding Testing V&V Usage Operating Instructions Operations
20 Waterfall is like Cannonball
21 Waterfall Summary
22 Iterative Development
23 Incremental Development
24 Iterative and Incremental Development
25
26 Iterative and Incremental Process R D C T R D C T R D C T R D C T R D C T R D C T Time
27 What is Iterative and Incemental Development?
28 Risks in Waterfall and Iterative Methods We do risky things first R I S K Iterative development Waterfall T I M E 28
29 Standish Report USA : $ billion per year is spent on failed and cancelled projects UK :12 out of 18 Large IT projects have failed
30 The Cost of Change in Waterfall and Iterative Methods WF Iterative
31 Wasted Features - Standish Report
32 Waterfall vs. Iterative & Incremental But... 32
33 TWO BRANCHES OF SOFTWARE DEVELOPMENT CAPABILITY MATURITY MODEL INTEGRATION (CMMI)
34
35
36
37
38 The History of CMMs 38
39 CMMI: 3 Complementary Constellations
40 DoD / Carnegie Melon University / Software Engineering Institute 40
41 DoD / Carnegie Melon University / Software Engineering Institute
42 SW Industry vs. NASA 6 SIGMA 3.4 Defects Per Million Opportunities DPMO
43 Characteristics of the Maturity Levels 43
44 Capability CMMI Model Representations Staged Continuous ML4 ML5 ML3 ML2 ML 1 Organization PA PA Process PA 44
45 Equivalence Staging Maturity Level 3
46 The Appraisal Method
47
48 TWO BRANCHES OF SOFTWARE DEVELOPMENT AGILE METHODOLOGIES
49
50 The Manifesto for Agile Software Development Individuals & Interactions Working Software Customer Collaboration Responding to Change Processes & Tools Comprehensive Documentation Contract Negotiation Following a Plan
51 Agile Manifesto February 2001, a subtle but deadly attack on Alistair Jim Martin Ward the old Cockburn Highsmith Fowler Cunningham Kent Beck Agility is the ability to both create and respond to change in order to profit in a turbulent business environment. Agility is the ability to balance flexibility and stability. TARTU murdes: väledad metoodikad
52 Agile is like Homing Missile
53 Agile Success & Hype
54 Agile Brand Name Methodologies
55 Agile 2001 vs vs Scrum; 3% Lean; 7% Other; 17% XP; 38% DSDM; 19% ASD; 22% FDD; 23% extreme Programming (XP): 38% 4% Scrum: 3% 58% 55
56 Agile Ecosystem
57 Standish Group 2012
58 Scrum & XP Scrum & Agile Whatever agile practices you like 58
59 Scrum and XP (most common practices) Pair programming Test-driven development Collective code ownership Coding standards
60 Scrum
61 The Founding Fathers 1995 Jeff Sutherland In collaboration with Jeff McKenna Ken Schwaber In collaboration with Chris Martin and Mike Smith Mike Beedle and Martine Devos Scrum 61
62 The Goal of Scrum Manage Complexity, Unpredictability and Change through Visibility, Inspection and Adaptation
63 Scrum Explained
64 Introduction by Ken Schwaber Scrum is not a methodology. Scrum does not provide the answers to how to build quality software faster. Scrum is a framework within which the game of product development is played. Your team plays and how good or notgood it is becomes highly visible. Your team gets to continuously improves itself. 64
65 What is Scrum? Definition from rugby football: a scrum is a way to restart the game after an interruption, where the forwards of each side come together in a tight formation and struggle to gain possession of the ball when it is tossed in among them
66 Scrum - an Agile Process SCRUM is an agile, lightweight process for managing and controlling software and product development in rapidly changing environments. Iterative, incremental process Team-based approach developing systems/ products with rapidly changing requirements Controls the chaos of conflicting interest and needs Improve communication and maximize cooperation Protecting the team form disruptions and impediments A way to maximize productivity
67 Characteristics Self-organizing teams Product progresses in a series of month-long sprints Requirements are captured as items in a list of product backlog No specific engineering practices prescribed Uses generative rules to create an agile environment for delivering projects One of the agile processes
68 Scrum in a Nutshell
69 See the Big Picture It s all about the business, not the technology
70 Scrum Today: 1-2 weeks 70
71 Scrum Framework Roles Product owner ScrumMaster Team Ceremonies Sprint planning Sprint review Sprint retrospective Daily scrum meeting Artifacts Product backlog Sprint backlog Burndown charts
72 picture by exfordy Scrum Roles
73 The Boss
74 The Boss
75 Product Owner Owner of project vision Represents the customer
76 Product Owner Define the features of the product Decide on release date and content Be responsible for the profitability of the product (ROI) Prioritize features according to market value Adjust features and priority every iteration, as needed Accept or reject work results
77 Scrum Master Servant leader Team protector Troubleshooter Scrum guide
78 The ScrumMaster Represents management to the project Responsible for enacting Scrum values and practices Removes impediments Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Shield the team from external interferences
79 The Team Small (5 9 people) Colocated - Cross-functional Self-organized - Full-time
80 Typically 5-9 people Cross-functional: The Team Programmers, testers, user experience designers, etc. Members should be full-time May be exceptions (e.g., database administrator) Teams are self-organizing Ideally, no titles but rarely a possibility Membership should change only between sprints
81 Self-Organized-Team vs. Traditional Organisation Self ManagingTeams customer-driven multi-skilled workforce few job descriptions Information widely shared Few levels of management Whole-business focus Shared goals Seemingly chaotic Purpose achievement emphasis High worker commitment Continuous improvements Self-controlled Values/principles based Traditional Organization management driven workforce of isolated specialists Many Job Descriptions Information limited Many levels of Management Function/department focus Segregated goals Seemingly organized Problem-solving emphasis High Management commitment Incremental improvements Management-controlled Policy/procedure based Source: "Leading self-directed work teams" by Kimball Fisher 81
82 Team Size
83 Communicaton Pathways Increase Geometrically with Team Size Why a complete graph has n(n 1)/2 edges?
84 The Team is Empowered and Accountable In Scrum, the team is both empowered and accountable to deliver the goods. The team does their job when they self-organize, selfmanage and self-achieve the objectives of the Sprint. For many organizations, this turns things upside down. The hierarchical-technical-management-directive approach is essentially eliminated with Scrum. The Product Owner now sets the objectives and priorities, the team figures out how to achieve them, and no one need tell them how to do that along the way.
85 Scrum Framework Roles Product owner ScrumMaster Team Ceremonies Sprint planning Sprint review Sprint retrospective Daily scrum meeting Artifacts Product backlog Sprint backlog Burndown charts
86 Scrum Meetings
87 Sprint Planning Meeting Outcome is Committed Product Backlog Items (PBIs) and Subordinate Sprint Tasks
88 Sprints Steady pull of business value Inspect and Adapt
89 Sprints Scrum projects make progress in a series of sprints Typical duration is 1 4 weeks or a calendar month at most A constant duration leads to a better rhythm Product is designed, coded, and tested during the sprint
90 No Changes During a Sprint Change Plan sprint durations around how long you can commit to keeping change out of the sprint
91 The Sprint Goal A short statement of what the work will be focused on during the sprint Database Application Life Sciences Support features necessary for population genetics studies. Make the application run on SQL Server in addition to Oracle. Financial services Support more technical indicators than company ABC with real-time, streaming data.
92 Sprint Planning meeting Stand-ups Development Testing Sprint (1 or 2 weeks) Showcase Retrospective Planning meeting
93 Sprint Planning Team selects items from the product backlog they can commit to completing Sprint backlog is created Tasks are identified and each is estimated (1-16 hours) Collaboratively, not done alone by the ScrumMaster High-level design is considered As a vacation planner, I want to see photos of the hotels. Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)
94 Sprint Planning Team capacity Product backlog Business conditions Current product Technology Sprint planning meeting Sprint prioritization Analyze and evaluate product backlog Select sprint goal Sprint planning Decide how to achieve sprint goal (design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours Sprint goal Sprint backlog
95
96
97 Daily Scrum The heartbeat of Scrum
98 The Daily Scrum Parameters Daily 15-minutes Stand-up Not for problem solving Whole world is invited Only team members, ScrumMaster, product owner, can talk Chickens and Pigs Helps avoid other unnecessary meetings
99 Everyone Answers 3 Questions What did you do yesterday? What will you do today? Is anything in your way? 1 2 3
100 Pigs and Chickens Product Owner Scrum Master Team Members Users Managers Marketing
101 Sprint Review Satisfy Product Owner Get feedback on product
102 Sprint Review Informal, no slides Whole team participates The world is invited picture by oskay
103 The Sprint Review Team presents what it accomplished during the sprint Typically takes the form of a demo of new features or underlying architecture Informal 2-hour prep time rule No slides Whole team participates Invite the world
104 The Sprint Review Team demonstrates working software to product owner Product owner accepts or rejects completed work Result should be potentially shippable
105 Sprint Retrospective
106 Sprint Retrospective Team meets to review: What is working? What is not working? Team adds tasks for immediate actions for working better
107 Sprint Retrospective Periodically take a look at what is and is not working Typically minutes Done after every sprint Whole team participates ScrumMaster Product owner Team Possibly customers and others
108 Scrum Framework Roles Product owner ScrumMaster Team Ceremonies Sprint planning Sprint review Sprint retrospective Daily scrum meeting Artifacts Product backlog Sprint backlog Burndown charts
109 ARTIFACTS 109
110 User Stories Mike Cohn 110
111 User Stories Mike Cohn = value for user 111
112 Stories at Different Levels of Granularity Project Level Story Iteration Level Story Release Level Story Iteration 1 4 weeks Release 1 12 weeks Project 1 many weeks
113 Stories, Features and Epics Feature 113
114 Product Backlog
115 First an Idea 115
116 Then a Vision 116
117 The Vision 117
118 Then a Product Backlog 118
119 Product Backlog The Product Backlog answers following questions: What? When? For who? 119
120 Product Backlog Is only a FORECAST!-> is not exact
121 Evolution of Product Backlog
122 A Sample Product Backlog Backlog item Estimate Allow a guest to make a reservation 3 As a guest, I want to cancel a reservation. 5 As a guest, I want to change the dates of a reservation. As a hotel employee, I can run RevPAR reports (revenue-per-available-room) 3 8 Improve exception handling
123 A Sample Sprint Backlog Tasks Mon Tues Wed Thur Fri Code the user interface Code the middle tier Test the middle tier Write online help 12 Write the foo class Add error logging 8 4
124 Sprint Burn down Chart Depicts the total Sprint Backlog hours remaining per day Shows the estimated amount of time to release Ideally should burn down to zero to the end of the Sprint Actually is not a straight line Can bump UP
125 Hours Tasks Code the user interface Code the middle tier Test the middle tier Write online help Mon Tues Wed Thur Fri Mon Tue Wed Thu Fri
126 Scrum Summary The Product Owner sets a List of Features called Product Backlog ❶ During the Sprint Planning, the Product Owner determines a piece of the top of that list: the Sprint Backlog; and decide how to implement it. The Team has a time-box to reach this goal: the Sprint 126
127 Scrum Summary ❷ Each day, the Team measures its progress during a 15 meeting: the Daily Scrum During the whole project, the Scrum Master ensures that the Team is still focused on its objective. At the end of the Sprint, the work has to be potentialy shipable. This work is considered as done. 127
128 Scrum Summary ❸ The Sprint ends with the Sprint Review and the Retrospective. The Scrum process is done when all Stories are implemented, or the budget is consummed, or when the time is over. 128
129 RUP and Agile Methodologies
130 RUP What? How? Do! Deliver! Milestones Understand the problem Understand the solution Solution ready? Acceptance from the customer 130
131 Sequential RUP "Waterfall"
132 Pure Iterative RUP
133 RUP RUP lifecycle is serial in the large and iterative in the small When all of the sides of the parallelogram "collapse" into a diagonal line, a "pure waterfall" approach results with disciplines are distributed across iterations.
134 RUP Scrum Construction
135 SUMMARY
136 There are no silver bullets
137 Notice: Methodologies do not write Code
138 Dimensions Affecting Method Selection
139 Right-size" the Process Allow projects to "right-size" the process they use; That is, allow projects to use "just enough" process. Users should be able to start with a small process, and as project needs expand, to grow the process to address those needs. 139
Getting Agile with Scrum. Mike Cohn - background
Getting Agile with Scrum Mike Cohn Mountain Goat Software mike@mountaingoatsoftware.com 1 Mike Cohn - background 2 We re losing the relay race The relay race approach to product development may conflict
More informationAn Introduction to Scrum
An Introduction to Scrum An Introduction to Scrum Presented by We re losing the relay race The relay race approach to product development may conflict with the goals
More informationAn Introduction to Scrum. The Agile Manifesto a statement of values
An Introduction to Scrum Presented by Wayne Allen Large portions of this presentation of this presentation are used w ith permission from Mike Cohn Mountain Goat Soft ware, LL C The Agile Manifesto a statement
More informationGetting Agile with Scrum. We re losing the relay race
Getting Agile with Scrum Mike Cohn 6 June 2014 1 We re losing the relay race The relay race approach to product development may conflict with the goals of maximum speed and flexibility. Instead a holistic
More informationAgile Software Development with Scrum. Jeff Sutherland Gabrielle Benefield
Agile Software Development with Scrum Jeff Sutherland Gabrielle Benefield Agenda Introduction Overview of Methodologies Exercise; empirical learning Agile Manifesto Agile Values History of Scrum Exercise:
More informationScrum. SE Presentation. Anurag Dodeja Spring 2010
Scrum SE Presentation by Anurag Dodeja Spring 2010 What is Scrum? Scrum is an agile software development framework. Work is structured in cycles of work called sprints, iterations of work that are typically
More informationIntroduction to Agile Scrum
Introduction to Agile Scrum by Julia M. Lobur Penn State Harrisburg CMPSC 487W Fall 2015 Introduction to Scrum Learning Goals Relationship of Scrum to other Agile methods Scrum Framework Scrum Roles Scrum
More informationWhat is Scrum? Scrum Roles. A lean approach to software development. A simple framework. A time-tested process
What is Scrum? From http://www.scrumalliance.org/pages/what_is_scrum A lean approach to software development Scrum is an agile software development framework. Work is structured in cycles of work called
More informationD25-2. Agile and Scrum Introduction
D25-2 Agile and Scrum Introduction How to Use this Download This download is an overview of a discussion Intertech has with clients on Agile/Scrum This download has an overview of Agile, an overview of
More informationGetting Agile with Scrum
Getting Agile with Scrum Mike Cohn November 11, 2008 1 Mike Cohn - background 2 Agenda Overview of Scrum Product backlogs Sprints and sprint backlog Tracking progress Scrum meetings 3 The Agile Manifesto
More informationCSSE 372 Software Project Management: More Agile Project Management
CSSE 372 Software Project Management: More Agile Project Management Shawn Bohner Office: Moench Room F212 Phone: (812) 877-8685 Email: bohner@rose-hulman.edu Learning Outcomes: Plan Create a plan for
More informationAgile Project Management
Agile Project Management with Bill Doescher, PMP, MBA, CSM Pi Principal i lconsultant tand Product tdevelopment tdirector Bill Doescher, PMP, CSM Bill Doescher is a Principal Consultant and Product Development
More informationMike Cohn - background
Scrum for Video Game Development 1 Mike Cohn - background 2 What is Scrum? One of the agile processes Iterative and incremental Produces demonstrable working software every two to four weeks Results- and
More informationSelecting a Development Process. Agenda
Selecting a Development Process Mike Cohn Founder Mountain Goat Software Boulder, CO mike@mountaingoatsoftware.com Agenda The processes Team Software Process Scrum Extreme Programming The Unified Process
More informationCapstone Agile Model (CAM)
Capstone Agile Model (CAM) Capstone Agile Model (CAM) Approach Everything we do within the Capstone Agile Model promotes a disciplined project leadership process that encourages frequent inspection and
More information"Bezpieczny Projekt"
Konferencja "Bezpieczny Projekt" Wrocław 22 czerwca 2010 www.omec.pl Software Development with Agile SCRUM Chandrashekhar Kachole 22 nd of June 2010 1 Let s keep the cell phones in Silent mode 2 Agenda
More informationIntroduction to Agile and Scrum
Introduction to Agile and Scrum Matthew Renze @matthewrenze COMS 309 - Software Development Practices Purpose Intro to Agile and Scrum Prepare you for the industry Questions and answers Overview Intro
More informationAgile Project Management: Adapting project behaviors to the software development environment
Agile Project Management: Adapting project behaviors to the software development environment with Bill Doescher, PMP, CSM PrincipalConsultant and Product Development Director Business Management Consultants
More informationImad Alsadeq, Qatar, May 2013 OPM3, MSP, PMP, PMOC, PMI-RMP, MCP
Qatar, May 2013 Imad Alsadeq, OPM3, MSP, PMP, PMOC, PMI-RMP, MCP PMI is a registered trade and service mark of the Project Management Institute, Inc. 2013 Permission is granted to PMI for PMI Marketplace
More informationAgile Scrum Workshop
Agile Scrum Workshop What is agile and scrum? Agile meaning: Able to move quickly and easily. Scrum meaning: a Rugby play Agile Scrum: It is an iterative and incremental agile software development framework
More informationAgile Development Overview
Presented by Jennifer Bleen, PMP Project Services Practice of Cardinal Solutions Group, Inc. Contact: Agile Manifesto We are uncovering better ways of developing software by doing it and helping others
More informationUnderstanding agile project management methods using Scrum H. Frank Cervone Purdue University Calumet, Hammond, Indiana, USA
The current issue and full text archive of this journal is available at www.emeraldinsight.com/1065-075x.htm OCLC 18 Accepted October 2010 MANAGING DIGITAL LIBRARIES: THE VIEW FROM 30,000 FEET Understanding
More informationIssues in Internet Design and Development
Issues in Internet Design and Development Course of Instructions on Issues in Internet Design and Development Week-2 Agile Methods Saad Bin Saleem PhD Candidate (Software Engineering) Users.mct.open.ac.uk/sbs85
More informationAgile in Financial Services A Framework in Focus
Agile in Financial Services A Framework in Focus John B. Hudson, B.Sc, PMP, CSM PMI NJ Chapter February 19, 2013 19 Feb 2013 1 Objectives 1. Agile Development an Overview 2. The Agile Enterprise Infrastructure
More informationAgile Project Management
Agile Project Management Overview Fabrizio Morando Application Development Manager martedì 20 novembre 2012 What is Agile? Agile is used to denote the ability of Agile Methods to respond to changing requirement
More informationPMP vs. Scrum Master
PMP vs. Scrum Master Compatible or Incompatible? Presented by: Karen Little, PMP, CSM, CBAP, ITIL, MCP, MBA Copyright 2007 by Karen Little 1 Agenda Introductions Background on Agile and SCRUM Methodologies
More informationAgile Software Development. Stefan Balbo / Patrick Dolemieux
Agile Software Development Stefan Balbo / Patrick Dolemieux Agile Software Development Stefan Balbo / Patrick Dolemieux Content Why go Agile? Introduction to Scrum - Process - Roles Agile Estimating and
More informationAgile Software Development
Agile Software Development Application in the Medical Device Industry Kelly Weyrauch Medtronic, Inc. (29 April 2008) Introduction Purpose Provide an introduction to Agile Software Development as it applies
More informationAgile with XP and Scrum
Agile with XP and Scrum Amit Goel National Agile Software Workshop @ Indore Agile India Conference Agile Software Community of India Disclaimer and Credits Most of material in this presentation has been
More informationScrumMaster Certification Workshop: Preparatory Reading
A S P E S D L C Tr a i n i n g ScrumMaster Certification Workshop: Preparatory Reading A WHITE PAPER PROVIDED BY ASPE ScrumMaster Certification Workshop: Preparatory Reading Greetings, Potential Certified
More informationLean Agile Scrum Business Value Development and Delivery using Agility. Brenden McGlinchey Software Done Right, Inc. brenden@softwaredoneright.
Lean Agile Scrum Business Value Development and Delivery using Agility Brenden McGlinchey Software Done Right, Inc. brenden@softwaredoneright.net High yield software engineering team Active Customer Involvement
More informationAdapting Agile Software Development to Regulated Industry. Paul Buckley Section 706 Section Event June 16, 2015
Adapting Agile Software Development to Regulated Industry Paul Buckley Section 706 Section Event June 16, 2015 Agenda FDA s expectations for Software Development What is Agile development? Aligning Agile
More informationLEAN AGILE POCKET GUIDE
SATORI CONSULTING LEAN AGILE POCKET GUIDE Software Product Development Methodology Reference Guide PURPOSE This pocket guide serves as a reference to a family of lean agile software development methodologies
More informationAtern The latest version of the DSDM approach which makes DSDM appropriate to all types of project.
THE AGILE PROJECT LEADER S DICTIONARY This dictionary attempts to de-mystify the jargon around the world of Agile projects. Part 1 translates common Agile terms into more traditional words. Part 2 translates
More informationHow to manage agile development? Rose Pruyne Jack Reed
How to manage agile development? Rose Pruyne Jack Reed What will we cover? Introductions Overview and principles User story exercise Retrospective exercise Getting started Q&A About me: Jack Reed Geospatial
More informationThe Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. July 2013. Developed and sustained by Ken Schwaber and Jeff Sutherland
The Scrum Guide The Definitive Guide to Scrum: The Rules of the Game July 2013 Developed and sustained by Ken Schwaber and Jeff Sutherland Table of Contents Purpose of the Scrum Guide... 3 Definition of
More informationAgile Methodologies XP and Scrum
Agile Methodologies XP and Scrum Introduction into Software Engineering Lecture 22 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Problem: How to we Control Software Development?
More informationScrum for Managers, Zurich March 2010
Scrum for Managers Microsoft Corporation / TechTalk Zurich Switzerland March 2010 About Mitch Lacey Mitch Lacey 13+ years of program and project management experience Microsoft Program Manager 2001 2006
More informationHistory of Agile Methods
Agile Development Methods: Philosophy and Practice CPSC 315 Programming Studio Fall 2010 History of Agile Methods Particularly in 1990s, some developers reacted against traditional heavyweight software
More informationAgile to the Bone. Introduction to Agile by Pietari Kettunen
Agile to the Bone Introduction to Agile by Pietari Kettunen Agenda Problem with traditional software engineering Why Agile is the solution? Roots of Agile Values of Agile Common implementations Scrum Kanban
More informationScrum Guidelines. v.2 2011 W W W. S C R U M D E S K. C O M
Scrum Guidelines v.2 2011 W W W. S C R U M D E S K. C O M WHY Agile Ceremonies Agile project is developed in repeatable ceremonies that give rhythm to delivery. Product Strategy Once per year Release Planning
More informationSprint with Scrum and get the work done. Kiran Honavalli, Manager Deloitte Consulting LLP March 2011
Sprint with Scrum and get the work done Kiran Honavalli, Manager Deloitte Consulting LLP March 2011 Contents About Deloitte Consulting 3 Executive summary 4 About Scrum 5 Scrum phases 8 Lessons learned
More informationWater-Scrum-Fall Agile Reality for Large Organisations. By Manav Mehan Principal Agile consultant Manav.Mehan@tcs.com
Water-Scrum-Fall Agile Reality for Large Organisations By Manav Mehan Principal Agile consultant Manav.Mehan@tcs.com Interests and Experience Leading Change and Transformation in Large, Complex organisations
More informationIntroduction to Agile Software Development. EECS 690 Agile Software Development
Introduction to Agile Software Development EECS 690 Agile Software Development Agenda Research Consent Forms Problem with Software Engineering Motivation for Agile Methods Agile Manifesto Principles into
More informationAgile Scrum Training. Nice to meet you. Erik Philippus. Erik Philippus (1951) www.improvement-services.nl www.agile-architecting.com.
Erik Philippus IMPROVEMENT BV erik@agile-architecting.com 1 IMPROVEMENT BV Nice to meet you Erik Philippus (191) IMPROVEMENT BV 3 years of experience in industrial automation Foxboro, ESA, Philips Medical,
More informationIntroduction to Agile Software Development Process. Software Development Life Cycles
Introduction to Agile Software Development Process Presenter: Soontarin W. (Senior Software Process Specialist) Date: 24 November 2010 AGENDA Software Development Life Cycles Waterfall Model Iterative
More informationThe Agile Manifesto is based on 12 principles:
The Agile Manifesto is based on 12 principles: Customer satisfaction by rapid delivery of a useful product solution Welcome changing requirements, even late in development Working products are delivered
More informationAgile QA s Revolutionary Impact on Project Management
Agile QA s Revolutionary Impact on Project Management Introduction & Agenda Rachele Maurer Agile Coach, Platinum Edge Inc. PMP, CSM, PMI-ACP Agenda A quick overview of agile Current QA practices QA using
More informationAGILE SOFTWARE DEVELOPMENT: INTRODUCTION, CURRENT STATUS & FUTURE Pekka Abrahamsson 23.11.2005 Jyväskylä
AGILE SOFTWARE DEVELOPMENT: INTRODUCTION, CURRENT STATUS & FUTURE Pekka Abrahamsson 23.11.2005 Jyväskylä Fact corner: SME of 250 developers Mobile & desktop sw Products sold globally EXAMPLE OF AN INNOVATIVE
More informationCourse Title: Planning and Managing Agile Projects
Course Title: Planning and Managing Agile Projects Course ID: BA15 Credits: 21 PDUs Course Duration: 3 days (Live in person class only) Course Level: Basic/Intermediate Course Description: This 3-day course
More informationWaterfall to Agile. DFI Case Study By Nick Van, PMP
Waterfall to Agile DFI Case Study By Nick Van, PMP DFI Case Study Waterfall Agile DFI and Waterfall Choosing Agile Managing Change Lessons Learned, Sprints Summary Q and A Waterfall Waterfall Waterfall
More informationSAFETY & RESILIENCE ISSUES IN AUTOMOTIVE SOFTWARE DEVELOPMENT PANEL
SAFETY & RESILIENCE ISSUES IN AUTOMOTIVE SOFTWARE DEVELOPMENT PANEL 1 Safety Panel when 26262 will be issued, enforced? What about 61508? by whom, which authorities? who and how will verify conformance?
More informationIngegneria del Software Corso di Laurea in Informatica per il Management. Agile software development
Ingegneria del Software Corso di Laurea in Informatica per il Management Agile software development Davide Rossi Dipartimento di Informatica Università di Bologna The problem Efficiency: too much effort
More informationCourse Title: Managing the Agile Product Development Life Cycle
Course Title: Managing the Agile Product Development Life Cycle Course ID: BA25 Credits: 28 PDUs Course Duration: 4 days (with optional Executive session) Course Level: Intermediate/Advanced Course Description:
More informationAgile Project Management and Agile Practices Training; with a Scrum Project that you will do.
1 PMI Agile Certified Practitioner (PMI-ACP) workshop course details. We are unique and specialists in Agile! Your workshop trainer by passion and is a senior Agile Coach who coached many teams and Kanban
More informationSWEN - Software Engineering Network Donnerstag 06. Mai. 2010
SWEN - Software Engineering Network Donnerstag 06. Mai. 2010 Agile Requirements Engineering Blaise Rey-Mermet, EVOCEAN GmbH, 2010 My background Executive Roles Dept. Head - Requirements Management & Engineering
More informationSoftware Engineering Process Economy & Quality
Project delivery: Progress report Software Engineering Process Economy & Quality ETSF 01 http://cs.lth.se/etsf01 The SPA reports you RECEIVED Your actions on received feedback Excel format preferred Lecture
More informationSometimes: 16 % Often: 13 % Always: 7 %
SCRUM AT RIIS A Standish study found that only 20% of features in a typical system were used often or always and 45% of features were never used at all. The ability to embrace change is critical to reducing
More informationSECC Agile Foundation Certificate Examination Handbook
Versions 2.0 Version Date Remarks 1.0 12/4/2012 Initial version 2.0 3/8/2008 REVISION HISTORY Updated knowledge areas Added questions examples Updated suggested readings section Page 2 of 15 Version 2.0
More informationLaboratório de Desenvolvimento de Software
Laboratório de Desenvolvimento de Software FEUP/MIEIC, 2015/16 Ademar Aguiar Nuno Flores Rui Maranhão Hugo Ferreira Luís Teixeira url: moodle http://www.facebook.com/notes/facebook-engineering/visualizing-friendships/469716398919
More informationAgile Information Management Development
Agile Information Management Development Agile Project Management Characteristics Acceptance and even welcome of changing requirements Incremental product delivery Define, develop and deliver early and
More informationSCRUM BODY OF KNOWLEDGE (SBOK Guide)
A Guide to the SCRUM BODY OF KNOWLEDGE (SBOK Guide) 2013 Edition A Comprehensive Guide to Deliver Projects using Scrum TABLE OF CONTENTS TABLE OF CONTENTS 1. INTRODUCTION... 1 1.1 Overview of Scrum...
More informationLean QA: The Agile Way. Chris Lawson, Quality Manager
Lean QA: The Agile Way Chris Lawson, Quality Manager The Quality Problem Agile Overview Manifesto Development Methodologies Process Agile QA Lean QA Principles An Agile QA Framework Summary Q & A Agenda
More informationSoftware processes that are:
Agile Processes Software processes that are: Incremental (small software releases with rapid cycles) Cooperative (customer and developer working together with close communication) Straightforward (method
More informationScrum methodology report
Scrum methodology report Author: Tsholofelo Eunice Moitsheki Student number Tsholofelo Moitsheki (463642) Project Source and Documentation: http://kenai.com/downloads/dotsboxes/group%20report/dab5_scrum
More informationUSCIS/SPAS: Product Backlog Items and User Stories 4/16/2015. Dr. Patrick McConnell
USCIS/SPAS: Product Backlog Items and User Stories 4/16/2015 Dr. Patrick McConnell July 9, 2015 1 First, an old joke.. I can t identify an original source for this cartoon. As best as I can tell, the art
More informationAGILE & SCRUM. Revised 9/29/2015
AGILE & SCRUM Revised 9/29/2015 This Page Intentionally Left Blank Table of Contents Scrum Fundamentals Certified Course... 1 Scrum Developer Certified (SDC)... 2 Scrum Master Certified (SMC)... 3 Scrum
More informationAgile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 4 Scrum: Current Framework 1 Scrum: New Process Framework 1. A people-centric framework based on a set of values, principles, and practices that
More informationIntroduction to Agile
Chapter 1 Introduction to Agile Objectives: Define Agile software development Explain differences and similarities between various lightweight methodologies Learn the core principles of Agile Dispel common
More informationAgile Project Management Mapping the PMBOK Guide to Agile Practices. Michele Sliger michele@sligerconsulting.com Twitter: @michelesliger
Agile Project Management Mapping the PMBOK Guide to Agile Practices Michele Sliger michele@sligerconsulting.com Twitter: @michelesliger Michele Sliger Sliger Consulting, Inc. www.sligerconsulting.com Over
More informationAgile Software Development and Service Science
Agile Software Development and Service Science How to develop IT-enabled Services in an Interdisciplinary Environment Andreas Meier Institute of Applied Information Technology (InIT) Zurich University
More informationMM Agile: SCRUM + Automotive SPICE. Electronics Infotainment & Telematics
MM Agile: SCRUM + Automotive SPICE Electronics Infotainment & Telematics 20 Novembre, 2010 INDEX Introduction Why MM Agile Approach? How did we align classical and agile approach? How do we implement SCRUM?
More informationTraditional SDLC Vs Scrum Methodology A Comparative Study
Traditional SDLC Vs Scrum Methodology A Comparative Study M. Mahalakshmi 1, DR. M. Sundararajan 2 1 Research Scholar, St. Peter s University, Avadi, India 2 Asst. Professor, Department of Computer Science,
More informationThe Scrum software development for small project teams. Siim Nahkur, 14.05.2104
The Scrum software development for small project teams Siim Nahkur, 14.05.2104 Old model is not working... Classical methods of software development have many disadvantages: huge planning phase poor reaction
More informationA Viable Systems Engineering Approach. Presented by: Dick Carlson (richard.carlson2@boeing.com)
A Viable Systems Engineering Approach Presented by: Dick Carlson (richard.carlson2@boeing.com) Philip Matuzic (philip.j.matuzic@boeing.com) i i Introduction This presentation ti addresses systems engineering
More informationThe Basics of Scrum An introduction to the framework
The Basics of Scrum An introduction to the framework Introduction Scrum, the most widely practiced Agile process, has been successfully used in software development for the last 20 years. While Scrum has
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationA Glossary of Scrum / Agile Terms
A Glossary of Scrum / Agile Terms Acceptance Criteria: Details that indicate the scope of a user story and help the team and product owner determine done-ness. Agile: the name coined for the wider set
More informationIntroduction to Agile Software Development
Introduction to Agile Software Development Word Association Write down the first word or phrase that pops in your head when you hear: Extreme Programming (XP) Team (or Personal) Software Process (TSP/PSP)
More informationMastering the Iteration: An Agile White Paper
Rally Software Development Corporation Whitepaper Mastering the Iteration: An Agile White Paper Dean Leffingwell Abstract: The heartbeat of Agile development is the iteration the ability of the team to
More informationDigital Transformation of the Enterprise for SMAC: Can Scrum help?
Digital Transformation of the Enterprise for SMAC: Can Scrum help? Scope of this Report October 2015 In this paper, we consider the impact of the digital transformation on software development and whether
More informationScrum a tester s perspective
Scrum a tester s perspective Presentation to BCS Sigist 2010 Fran O Hara, O Practice Manager, Sogeti Ireland www.sogeti.ie www.uk.sogeti.com Agenda Introduction to Scrum Quality/Test challenges with Scrum
More informationThe Agile Glossary of Terms
ASPE RESOURCE SERIES The Agile Glossary of Terms The skills we teach drive real project success. Agile Glossary Words and terms common to Agile methods Copyright 2013 Davisbase Consulting Licensed to ASPE
More informationCertified Scrum Master Workshop
Learn, understand, and execute on the three overarching principles behind Scrum: iterative development, selfmanagement, and visibility. Even projects that have solid, well-defined project plans encounter
More informationAgile and the Seven Deadly Sins of Project Management
Agile and the Seven Deadly Sins of Project Management Mike Cohn February 15, 2011 Mike Cohn - background A cornucopia of agile processes Agile Processes Extreme Programming (XP) Scrum Crystal DSDM Lean
More informationScrum Guide. By Ken Schwaber, May, 2009
Scrum Guide By Ken Schwaber, May, 2009 Scrum has been used to develop complex products since the early 1990s. This paper describes how to use Scrum to build products. Scrum is not a process or a technique
More informationAgile Systems Engineering: What is it and What Have We Learned?
Agile Systems Engineering: What is it and What Have We Learned? March 2012 Dr. Suzette S. Johnson Agile Engineering Northrop Grumman Suzette.Johnson@ngc.com Getting To Know You! Dr. Suzette Johnson Northrop
More informationWHITEPAPER GET MORE WORK DONE: A MANAGER S GUIDE TO MIXING AGILE AND WATERFALL
WHITEPAPER GET MORE WORK DONE: A MANAGER S GUIDE TO MIXING AGILE AND WATERFALL Project management is shifting. Teams that were siloed before are now asked to work together to ease reporting pains and increase
More informationIntroduction to Scrum
Introduction to Scrum Recorded by Michael James [Existing slide with MJ] Welcome to Module 1 of CollabNet s Scrum Training Series: Introduction to Scrum. This is a brief introduction to topics that are
More informationwww.testing-solutions.com TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes
www. TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes What is Agile Development? There are various opinions on what defines agile development, but most would
More informationSoftware Requirements and Specification
Software Requirements and Specification Agile Methods SE3821 - Jay Urbain Credits: Beck, K. (1999). Extreme Programming Explained: Embrace Change. Boston, MA: Addison-Wesley. Beck, Kent; et al. (2001).
More informationApplying Agile Project Management to a Customized Moodle Implementation
Applying Agile Project Management to a Customized Moodle Implementation November 6, 2013 Presented by: Curtis Fornadley, PMP UCLA CCLE Coordinator Applying Agile Project Management to a Customized Moodle
More informationAgile Project Management and the Real World. Emily Lynema DLF Fall 2010 November 1, 2010
Agile Project Management and the Real World Emily Lynema DLF Fall 2010 November 1, 2010 Outline Why care about project management? Traditional vs. Agile What is Agile? What is Scrum? Agile case study:
More informationAgile Project Management
Agile Project Management Projekt-Kick-Off-Tage Hochschule Augsburg Martin Wagner, 15. März 2011 TNG Technology Consulting GmbH, http://www.tngtech.com Agile project management with Scrum Agenda Software
More informationUC Santa Barbara. CS189A - Capstone. Christopher Kruegel Department of Computer Science UC Santa Barbara http://www.cs.ucsb.
CS189A - Capstone Christopher Kruegel Department of Computer Science http://www.cs.ucsb.edu/~chris/ How Should We Build Software? Let s look at an example Assume we asked our IT folks if they can do the
More informationVision created by the team. Initial Business Case created. Cross functional resource meeting held. Agile alignment meeting
Help Tips Agile SDLC Product Backlog Daily Standup Sprint 1 Show and Tell 2 Week Sprint Sprint 2 Release1 (must haves) Retrospective Sprint 1 DONE! Sprint 3 Sprint 2 DONE! Sprint Backlog Sprint 3 DONE!
More informationAn Example Checklist for ScrumMasters
An Example Checklist for ScrumMasters Michael James (mj4scrum@gmail.com) 14 September 2007 (Revised 24 July 2012) A Full Time Facilitator? An adequate ScrumMaster can handle two or three teams at a time.
More informationCSPO Learning Objectives Preamble. Scrum Basics
CSPO Learning Objectives Preamble This document contains topics for the Certified Scrum Product Owner (CSPO) training course. The purpose of this document is to describe the minimum set of concepts and
More informationAgile and Secure: Can We Be Both?
Agile and Secure: Can We Be Both? OWASP AppSec Seattle Oct 2006 Keith Landrus Director of Technology Denim Group Ltd. keith.landrus@denimgroup.com (210) 572-4400 Copyright 2006 - The OWASP Foundation Permission
More informationProduct Development with Scrum
Product Development with Scrum XP San Diego January 6, 2005 By Paul Hodgetts, Agile Logic www.agilelogic.com Introductions Solutions for Delivering Your Projects: Agile Process Adoption Solutions Coaching,
More information