Agile Software Development. Stefan Balbo / Patrick Dolemieux
|
|
- Christian Golden
- 5 years ago
- Views:
Transcription
1 Agile Software Development Stefan Balbo / Patrick Dolemieux
2 Agile Software Development Stefan Balbo / Patrick Dolemieux
3 Content Why go Agile? Introduction to Scrum - Process - Roles Agile Estimating and Planning Scaling Scrum Agile Practices beyond Scrum Benefits Pitfalls and Best Practices Resources
4 Why go Agile? Development projects have progressed over time More complex More scope changes
5 Why go Agile? IT Project Survey (Standish 2009) Development process has stayed the same Inadequate process results in projects that 24% 44% 32% Success Failing Failure - Fail - Have poor quality - Are frustrating to work on - Take longer than expected
6 What is Agile Software Development? The Agile Manifesto (2001): Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
7 What is Scrum? Framework - for agile software development Key concepts: - Iterative and incremental - Small self-organizing teams - Short feedback loops - Priority by business value
8 Starting a Scrum Project - Envisioning Articulate the project vision Determine and prioritize goals and objectives Define incremental releases Get vision accepted by all stakeholders
9 Operations Dashboard for ArcGIS Project Vision Operations Dashboard for ArcGIS provides a common operational picture for monitoring an event or a system across a group of people within your organization. Project started in February 2012 The first release was delivered in January 2013.
10 Operations Dashboard for ArcGIS The Context Native Applications Android SDK ios SDK Java SE SDK OS X SDK Qt SDK Windows Store SDK WPF SDK Android API ios API Java SE API OS X API Qt API Windows Store API WPF API ArcGIS Runtime Core
11 Starting a Scrum Project - Release Planning Create a prioritized list of Epics Create a prioritized backlog of items (PBI s) - INVEST in your backlog - Independent, Negotiable, Valuable, Estimable, Small, Testable - User Story Mapping Estimate Get commitment to proceed renjith krishnan / FreeDigitalPhotos.net Example User Story (PBI): Create Map Package As a Map Author I want to package my map and data, so I can easily share them with other desktop users.
12 Grooming the Backlog As PBI s move to the top of the backlog - Break them up into smaller PBI s - Add detail and get them ready for the Iteration planning - UI design - Acceptance criteria Groom once an iteration with the team Flickr: sockmister
13 Operations Dashboard for ArcGIS - Releases
14 Operations Dashboard for ArcGIS - Backlog description
15 Scrum Framework Product Backlog Daily Scrum Scrum Questions: Done? Do? Impediments? Iteration Planning Iteration Backlog Iteration 3 weeks Done Potentially Shippable Product Iteration Retrospective Iteration Review
16 Responsibilities of a Scrum Team Cross-Functional (5-9 members) Agrees to iteration goal and specifies work results Empowered to do anything to reach the iteration goals - within the project guideline boundaries Organizes itself and its work Demos work results to the stakeholders renjith krishnan / FreeDigitalPhotos.net
17 Product Owner Responsibilities Defines product features Prioritizes product backlog Establishes, communicates and nurtures the vision Accepts or rejects work results Grooms the product backlog Product Owner is the - vision keeper - daily decision maker - single wringable neck
18 Scrum Master (Agile Coach) Responsibilities Ensures team is productive Enables close cooperation Removes barriers Shields team from interferences Ensures the process is followed Invites to Scrum meetings The Scrum Master is the - Shepherd - Bulldozer - servant leader
19 Operations Dashboard for ArcGIS - The Team Product Engineers Andy (Lead) - ME Nick (Test) - UK Shelly (API & Doc) - UK Developers Jeff (Lead) - ME Eric, Fred & Scott - CA Gunther - UK Doug (Product Owner) - CA Patrick (Scrum Master) - CA The team works in coordination with: Mara Documentation/Resources Center Coordinator Lindsay Release Coordinator David Product Manager Patrick Program Manager Scott, Clint, Jeff, Andy Stakeholders
20 Sprint planning Prerequisite: - PBI s considered in Sprint are fully defined Team effort Define Goals Select PBI s Determine implementation Define Tasks for each PBI - Dev - Test - Doc - Estimate tasks in hours (2-24)
21 Operations Dashboard for ArcGIS Sprint Planning Sprint Goals
22 Operations Dashboard for ArcGIS Sprint Planning PBI and Tasks
23 Operations Dashboard for ArcGIS Sprint Planning Task description
24 Agile estimating and tracking How long will it take? - Is a legitimate question - Based on past performance rather than guessing - Agile estimating works
25 Operations Dashboard for ArcGIS - Estimating Product Backlog Items Story points It is not time Based on 3 criterias Compare to baseline story(ies) Using Fibonacci suite (1,2,3,5,8,13) 13 story points is the maximum Effort Uncertainty Complexity Tasks Hours Use ideal time for estimates Only remaining hours are tracked Generally between 1-24 hours 24 hours maximum
26 Operations Dashboard for ArcGIS - Reports & Charts Sprint Burndown Chart
27 Operations Dashboard for ArcGIS - Reports & Charts Team Member Load Chart
28 Operations Dashboard for ArcGIS - Reports & Charts Epic Progress Report
29 Operations Dashboard for ArcGIS - Reports & Charts
30 Operations Dashboard for ArcGIS - Reports & Charts 30% 7% 10% 9% 44% Design Development Test Doc Event
31 Scaling Scrum Define Team Structure - Feature vs. Component Teams - Lean towards Feature Teams Establish Communities of Practice - Topics affecting many teams Filomena Scalice / FreeDigitalPhotos.net Hold Scrum of Scrums meetings - Share information between teams Look two to three iterations ahead - Coordinate between teams each iteration Use Epics to track and communicate - High level Stories
32 Scaling Scrum Define Team Structure - Feature vs. Component Teams - Lean towards Feature Teams Establish Communities of Practice - Topics affecting many teams Filomena Scalice / FreeDigitalPhotos.net Hold Dependency meetings - Share information between teams Look two to three iterations ahead - Coordinate between teams each iteration Use Epics to track and communicate - High level Stories
33 Agile Practices beyond Scrum Engineering - Design Patterns - Paired Programming - Test Automation - Test Driven Development - Continuous Integration - Refactoring Tools Design - User Centered Design - Agile Data Modeling - Domain Driven Design
34 Benefits Bring the maximum value to our users More productive Successful Projects Accurate Estimates Transparency to Stakeholders All team members participate Continuous process improvement
35 Pitfalls when using Scrum Backlog Items are too big Backlog Items not fully defined Team over-commits Unclear definition of Done Team is too large Distributed Teams Product owner proxies Team members assigned to multiple Scrum teams Too many hats Little or no Release Planning
36 Operations Dashboard for ArcGIS Best Practices Estimates Always have a baseline PBI in mind When a PBI is estimated at 13 story points, consider splitting it When a task is estimated at more than 24 hours, consider splitting it Miscellaneous Do design at the earliest Avoid having many tasks in progress unless there are impeded Avoid having unassigned tasks During a daily scrum: Speak loud and clear Be specific and concise Days off and working days on other projects and events Must be known in front of sprint Goal is to better balance the workload
37 Operations Dashboard for ArcGIS Definition of Done (DoD) Task is done when: Design Reviewed Published Implementation Coded Code reviewed Checked in Test Local tested Reported Documentation Reviewed Published PBI is done when: All tasks done Demoed to the Product Owner
38 Operations Dashboard for ArcGIS - How to be done at the end of a sprint? Product Engineers do bug verifying, regression testing, update documentation, start design until Developers give them things to test Test/Doc Sprint Implementation Developers stop implementing before the end of the sprint to: - Fix bugs - Help testing if necessary or review design - Look at next sprint PBI and review/estimate development tasks
39 Links, Tools and Literature Scrumworks by CollabNet [easy to use, focused Scrum Tool] Agile Software Development with Scrum - by Ken Schwaber and Mike Beedle [The first Scrum book] Scrum and XP from the Trenches - by Henrik Kniberg [very practical how-to-guide] Succeeding with Agile Software Development Using Scrum - by Mike Cohn (2010) [Helpful for larger scrum implementations] Lean Software Development - by Mary Poppendieck and Tom Poppendieck [A good intro to Lean] Agile Product Ownership in a Nutshell - Video by Henrik Kniberg
40 Summary Why go Agile? Introduction to Scrum - Process - Roles Agile Estimating and Tracking Scaling Scrum Agile Practices beyond Scrum Benefits Pitfalls and Best Practices Resources
41 QUESTIONS? Don t forget to fill the survey about this presentation
42
Scrum. 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
Introduction 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
Agile 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
Introduction 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
Agile 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
Scrum. The Essence. Tobias Mayer, http://agilethinking.net. Sonntag, 19. Februar 12
Scrum The Essence What is Scrum? Scrum is a framework that allows you to create your own lightweight process for developing new products. Scrum is simple. It can be understood and implemented in a few
Mariusz Chrapko. Before: Software Quality Engineer/ Agile Coach, Motorola, Poland. My Public Profile: http://www.linkedin.
Gathering Customer Requirements in an Agile Environment Mariusz Chrapko ReConf 2009, Munich Mariusz Chrapko Now: Process Consultant/ Agile Coach@Kugler Maag CIE, Stuttgart Supported Areas: - CMMI - SPICE/
Agile 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
SECC 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
Agile 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
RISK MANAGMENT ON AN AGILE PROJECT
BIO PRESENTATION W3 6/28/ 11:30 AM RISK MANAGMENT ON AN AGILE PROJECT Michele Sliger Rally Software Development Better Software Conference June 26 29, Las Vegas, NV USA Michele Sliger Michele Sliger has
Agile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series
Overview This is a 15-day live facilitator-led or virtual workshop is designed to prompt your entire team to work efficiently with Microsoft s Application Lifecycle Management solution based around Visual
What 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
Mike 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
Agile 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
D25-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
Agile 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:
Scrum 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
CSSE 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
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
Capstone 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
An 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.
www.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
Agile 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
ScrumMaster 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
Adapting 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
SWEN - 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
Scrum and Kanban 101
Scrum and Kanban 101 www.bebetterleader.com @jfiodorova What are your expectations What are the differences between Agile and Traditional? What do you know about Agile Two approaches to control any process:
What does it mean to be Agile. Marek Majchrzak, Andrzej Bednarz Wrocław, 11.10.2011
What does it mean to be Agile Marek Majchrzak, Andrzej Bednarz Wrocław, 11.10.2011 2 Traditional methods Assumptions: The customer knows what he wants The developers know how to build it Nothing will change
Introduction 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
SCRUM. A Tool from the Software World Can Improve Analytical Project Outcomes. By KyMBER WALTMUNSON
SCRUM A Tool from the Software World Can Improve Analytical Project Outcomes By KyMBER WALTMUNSON When jurisdictions undertake analytical work such as audits, budget analysis, program evaluation, and special
Agile 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
Kanban vs Scrum Making the most of both
Kanban vs Scrum Making the most of both JAOO, Aarhus Oct 6, 2009 Henrik Kniberg Agile/Lean coach @ Crisp, Stockholm Board of directors henrik.kniberg@crisp.se +46 70 4925284 Purpose of this presentation
The 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
Scrum and Testing The end of the test role Bryan Bakker 20 maart 2012
Scrum and Testing The end of the test role Bryan Bakker 20 maart 2012 voordracht georganiseerd door Discussiegroep Software Testing met de steun van Ingenieurshuis, Antwerpen Scrum and Testing... The end
Agile and lean methods for managing application development process
Agile and lean methods for managing application development process Hannu Markkanen 27.01.2012 1 Lifecycle model To support the planning and management of activities required in the production of e.g.
Course 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
Agile 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
Lean 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
An 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
Agile 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
Waterfall 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
Role of the Business Analyst in an Agile Project
Role of the Business Analyst in an Agile Project Agenda 1: Introduction to Agile 2: Focus on Agile Principles 3: Business Analysis and the agile process 4: Addressing challenges 5: Close off and recap
A 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
Introduction 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
Getting 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
1. CMMI and Scrum TWO BRANCHES OF SOFTWARE DEVELOPMENT
1. CMMI and Scrum TWO BRANCHES OF SOFTWARE DEVELOPMENT Enterprise Software Engineering Agenda 1. CMMI and Scrum 2. Kanban Software Engineering 3. Software Development Life Cycle 4. Secure Software Engineering
The 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
Introduction 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
BCS Foundation Certificate in Agile Syllabus
BCS Foundation Certificate in Agile Syllabus Version 1.5 March 2015 Change History Any changes made to the syllabus shall be clearly documented with a change history log. This shall include the latest
SCRUM 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...
An 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
Agile 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:
History 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
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Each percentage
How can I be agile and still satisfy the auditors?
How can I be agile and still satisfy the auditors? Welcome & Introductions Steve Ropa Steven.ropa@versionone.com Agile Coach Certified Scrum Master Certified Scrum Product Owner 19 years software development
AGILE & 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
Scrum 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
Agile 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
Agile and lean methods for managing application development process
Agile and lean methods for managing application development process Hannu Markkanen 24.01.2013 1 Application development lifecycle model To support the planning and management of activities required in
There are 3 main activities during each Scrum sprint: A planning meeting where: the Product Owner prioritizes user stories in the product backlog
There are 3 main activities during each Scrum sprint: A planning meeting where: the Product Owner prioritizes user stories in the product backlog that need to be implemented during the sprint the Team
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Total questions
Introduction to User Story Mapping. July 2015 COPYRIGHT 2015 AGILITY SOFTWARE 1
Introduction to User Story Mapping MARK NONEMAN, PROFESSIONAL SCRUM EXPERT AGILITY SOFTWARE MARK@AGILITYSW.COM @MARKNONEMAN July 2015 COPYRIGHT 2015 AGILITY SOFTWARE 1 Getting To Know You! Mark Noneman
Getting 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
CSPO 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
Agile Project Management By Mark C. Layton
Agile Project Management By Mark C. Layton Agile project management focuses on continuous improvement, scope flexibility, team input, and delivering essential quality products. Agile project management
Sometimes: 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
An Introduction to Agile Performance Management
! 1 An Introduction to Agile Performance Management by Jeffrey B. Rothman, Ph.D. An Introduction to Agile This is a high level introduction to Agile -- a well known productivity framework for software
Agile Software Development in the Large
Agile Software Development in the Large Jutta Eckstein 1 Large Large in... Scope Time People Money Risks We concentrate on Large Teams Large is relative 1, 2, 10, 100, 2000 People 2 Principles behind Agile
Answered: PMs Most Common Agile Questions
Answered: PMs Most Common Agile Questions Mark Kilby Agile Coach, Rally Software mkilby@rallydev.com 407.687.3350 (cell) Led Fortune 50 agile transitions in - Government - Technology - Healthcare - Insurance/Fina
Vision 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!
Course 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:
Water-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
The Agile Project Manager
The Agile Project Manager PMI Madrid, 29/1/2014 1 Jose Barato Consulting, Training and Tools in Project Management PMPeople (Managing Director) PMI Madrid Chapter (Director) PM-IB (founder, Vice-President)
Kanban. Marek Majchrzak, Andrzej Bednarz Wrocław, 07.06.2011
Kanban Marek Majchrzak, Andrzej Bednarz Wrocław, 07.06.2011 Why Kanban? Jim: Now we ve finally gone all-out Scrum! Fred: So how s it going? Jim: Well, it s a lot better than what we had before... Fred:...but?
LEAN 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
Agile 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
MM 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?
Agile 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,
Product 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,
No one has to change. Survival is optional. - W. Edwards Deming - Continue your Beyond Budgeting Journey with help from Agile, Lean and Scrum
No one has to change. Survival is optional. - W. Edwards Deming - Continue your Beyond Budgeting Journey with help from Agile, Lean and Helge Eikeland, Statoil, October 2010 Today s challenge is complexity
Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.
Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.com 1 About Coveros Coveros helps organizations accelerate the delivery
USCIS/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
Software 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
Topics covered. Agile methods Plan-driven and agile development Extreme programming Agile project management Scaling agile methods
Topics covered Chapter 3 Agile Software Development Agile methods Plan-driven and agile Extreme programming Agile project management Scaling agile methods 1 2 Need for rapid software Rapid software Changing
Agile Practitioner: PMI-ACP and ScrumMaster Aligned
Agile Practitioner: PMI-ACP and ScrumMaster Aligned The PMI Agile Certified Practitioner (PMI-ACP) ScrumMaster credential validates your ability to understand agile principles, agile concepts, and establishes
Mastering 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
Agile 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
An Agile Approach to Metrics :
An Agile Approach to Metrics : Applied Macromeasurements to Ensure On-Time Delivery This article challenges the value of traditional metrics for managing product development schedules and presents a reality-based
References: Hi, License: Feel free to share these questions with anyone, but please do not modify them or remove this message. Enjoy the questions!
Hi, To assist people that we work with in Scrum/Agile courses and coaching assignments, I have developed some Scrum study-questions. The questions can be used to further improve your understanding of what
Ingegneria 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
Applying Lean on Agile Scrum Development Methodology
ISSN:2320-0790 Applying Lean on Agile Scrum Development Methodology SurendRaj Dharmapal, Dr. K. Thirunadana Sikamani Department of Computer Science, St. Peter University St. Peter s College of Engineering
Selecting 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
Effektiver Tool-Einsatz
Effektiver Tool-Einsatz für Scrum-Projekte im Java-Umfeld Agile Softwareentwicklung Werte, Prinzipien, Methoden und Prozesse 13. OBJEKTspektrum Information Days 29. April 2010, München Gerhard Müller,
The traditional project management uses conventional methods in software project management process.
Volume 5, Issue 1, January 2015 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com Analysis of
Bridging the Gap Between Acceptance Criteria and Definition of Done
Bridging the Gap Between Acceptance Criteria and Definition of Done Sowmya Purushotham, Amith Pulla sowmya.sudha@gmail.com, amith.pulla@intel.com Abstract With the onset of Scrum and as many organizations
Scrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014
Scrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014 1 Goals Cover Material from our User Stories Book Chapter 15: Using Stories With Scrum Chapter 16: Additional
Agile Testing. Workshop. Tilo Linz, imbus AG
Workshop Tilo Linz, imbus AG 2014 imbus AG www.imbus.de Tilo Linz CoFounder and member of managing board imbus AG President ISTQB (2002-2005) Chairman German Testing Board e.v. (2002-2013) Author Softwaretest
Agile Methods. Introduction to. AAddison-Wesley. Sondra Ashmore, Ph.D. Kristin Runyan. Capetown Sydney Tokyo Singapore Mexico City
Introduction to Agile Methods Sondra Ashmore, Ph.D. Kristin Runyan AAddison-Wesley Upper Saddle River, NJ Boston Indianapolis San Francisco New York Toronto Montreal London Munich Paris Mad Capetown Sydney
ScrumMaster or Armchair Psychologist Scrum Fundamentals Webinar Q&A March 9, 2016
ScrumMaster or Armchair Psychologist Scrum Fundamentals Webinar Q&A March 9, 2016 As a ScrumMaster, one of your responsibilities is "Causing change that increases the productivity of the Scrum Team." What