2 SPRiNT it SPRiNT it Gesellschaft für Lösungen Tainings Coaching Certified Master Trainings Sprint Runner ( Planning Tool) Internet Development
3 Agenda Complexity and Agile Underpinnings Overview Responsibilities Planning Agile Implementations Teams and Meetings Day in the Life of a Master and CMM, and XP
4 Agile Alliance Overview Values of Agile Alliance individuals and interactions over processes and tools working software over comprehensive documentation customer collaboration over contract negotiation responding to change over following a plan While there is value in the items on the right, we value the items on the left more.
5 Origins of Agile The New, New Product Development Game* Time Boxes Iterative, Incremental Development Smalltalk Engineering Tools, XP * Harvard Business Review, Jan. 1986, Takeuchi and Nonaka
6 Overview Empirical management & control process inspect and adapt feedback loops Used to build software, embedded software, telephone switches, FDA life critical software, mission critical software in organizations of up to 2,000 and projects of over 3,000. CMM Level3, ISO 9001/R Over 5300 Certified Masters Used by Sun Microsystems, Microsoft, Cisco, Symantec, Federal Reserve Bank, Lockheed Martin, CBOE, BBC, CNA, Siemens, Nokia, Covad, ClearChannel, Arbitron, Yahoo, Wildcard Systems; CapitalOne, TransUnion, and, Extremely simple but very hard.
7 Complexity assessment graph Far from Agreement Close to Agreement Anarchy Complicated Complex Simple Complicated Close to Certainty Technology Far from Certainty
10 Roles Activity Owner Responsibilities Manage the vision Product Owner The Product Owner establishes, nurtures and communicates the product vision. He achieves initial and on-going funding for the project by creating initial release plans and the initial Product Backlog. Manage the ROI Product Owner The Product Owner monitors the project against its ROI goals and an investment vision. He updates and prioritizes the Product Backlog to ensure that the most valuable functionality is produced first and built upon. He prioritizes and refines the Product Backlog and measures success against expenses. Manage the development iteration Team Manage the process Master During an iteration the team selects and develops the highest-priority features on the Product Backlog. Collectively, the team expands Product Backlog items into more explicit tasks on a Sprint Backlog and then manages its own work and self-organizes around how it desires to complete the iteration. The team manages itself to its commitments. The Master is responsible for setting the team up for success by ensuring the project and organizational culture are optimized for meeting the ROI goals of the project. This involves organizing a Sprint Planning Meeting (during which the team expands Product Backlog into Sprint Backlog), a Sprint Review Meeting (during which the newly developed functionality is demonstrated), shielding the team from outside disturbances, holding brief Daily meetings, and removing obstacles to progress. Manage the release Product Owner The Product Owner makes decisions about when to create an official release. For a variety of reasons it may not be desirable to release at the conclusion of every increment. Similarly, if an official release is planned for after the fifth increment it may be released (with fewer features) after the fourth increment in order to respond to competitive moves or capture early market share. The Product Owner makes these decisions in a manner consistent with the investment vision that has been established for the project.
11 As a Master, you are responsible for: Removing the barriers between development and the customer so the customer directly drives development Teaching the customer how to maximize ROI and meet their objectives through Improving the lives of the development team by facilitating creativity and empowerment Improving the productivity of the development team in any way possible and, Improving the engineering practices and tools so each increment of functionality is potentially shippable. Leader and Facilitator
12 Most projects deliver software every 6 to 18 months. reduces this to many 1 month deliveries to increase control via inspect/adapt. This puts stress on the team and organization, exposing underlying problems and limitations. The Master s job is to prioritize these problems and help the organization overcome them to get better at software development, managing software investments, and becoming a community to work in.
13 and the Master is a simple iterative, incremental skeleton with some rules. Equipped with a resolute, patient Master, can be used to transform software development into a profession, projects into Valuable endeavors, and development organizations into communities that people look forward to working in. It takes time. Remember that a dead Master is a useless Master. Remember that is just a framework. It doesn t fail. Sometimes people can t stand what it exposes. Masters are the key to its degree of success in transforming organizations.
14 Agile Skeleton Doing the Right Thing Easy to implement within 1 day Improves ROI Solves customer involvement Removes floundering and politics
15 Building the Thing Right More time to implement Solid engineering practices Solid engineering infrastructure XP
16 Plan the project WHY plan?? Lay out a common set of understandings from which emergence, adaptation and collaboration occur. Establish expectations that progress will be measured against. Convince a source of funding that the ROI of this project is worthwhile.
17 Product Backlog List of functionality, technology, issues Issues are placeholders that are later defined as work Prioritized, estimated More detail on higher priority backlog One list for multiple teams Product Owner responsible for priority Anyone can contribute Maintained and posted visibly Derived from Business Plan or Vision Statement, which sometimes have to be created with customer
18 Prioritize Product Backlog Attributes: Cost (ITD s), Tests, Value ($, H/M/L, x/1000) Sort by Value allocate your planning time 60% to top 20% in value, 30% to next 20%, and 10% to remainder Create Calculated Priority from value/cost Re-sort on Calculated Priority Manually adjust positions of product backlog items to fine tune 80% of the value comes from 20% of the functionality 60% of the functionality delivered in successful projects is rarely or never used.
19 Architecture/Infrastructure Allocate time for architecture and infrastructure development frontloads this development onto highest priority Sprints First Sprint develop business functionality that keeps customer engaged and tests architecture and infrastructure
20 Teams Self-organizing Cross-functional with no roles Seven plus or minus two Responsible for committing to work Authority to do whatever is needed to meet commitment Open, collocated space Resolution of conflicts
22 Sprint Planning Meeting Product Backlog Team Capabilities Business Conditions Technology Stability Executable Product Increment Review, Consider, Organize Next Sprint Goal Product Backlog Sprint Backlog
23 Sprint Planning Meeting Rules 1 day 1st - 4 hours max. for team to select Product Backlog and sets goal with Product Owner 2nd - 4 hours max. for team to define Sprint Backlog to build functionality Anyone can attend, but primary conversation and work is between team and Product Owner
24 Sprint Planning Meeting Part 1 Four hour max. meeting Defines what to build in the next Sprint Attended by Product Owner, team, customers, management TEAM DEFINES a SPRINT GOAL!! Team selects as much Product Backlog as it believes it can develop during the next Sprint Estimates may be revised upon review Lower priority backlog may be included if appropriate and Product Owner agrees Estimated effort/cost for selected product backlog items is a budget that team manages to; negotiate with Product Owner before exceeding.
25 Sprint Goal A Sprint Gaol is a theme for the Sprint: Support Features necessary for population genetics studies Prove the concept that was delivered by Architects Make the application run on SQL Server in addition to Oracle
26 Sprint Planning Meeting Part 2 Four hour max. meeting. Defines how to build the product functionality into a product increment in the next Sprint. This list is called the Sprint Backlog. Attended by Product Owner, team, development management Design is extended in this session. Team defines Sprint Backlog, consisting of all tasks that need to be completed during Sprint. Team members sign up for work and estimate their tasks. Tasks are 1-16 hours long; if longer, breakdown into more granularity.
27 Sprint Backlog Tasks to turn product backlog into working product functionality Tasks are estimated in hours, usually 1-16 Tasks with more than 16 hours are broken down later Team members sign up for tasks, they aren t assigned (be patient, just wait!) Estimated work remaining is updated daily Any team member can add, delete or change the Sprint Backlog (theirs or new) Work for the Sprint emerges If work is unclear, define a Sprint Backlog with a larger amount of time break it down later. Update work remaining as more is known, as items are worked
28 Sprint Backlog If the team believes that this is too much, they can meet again with the Product Owner
29 Monitor the task board
30 Another sample task board
31 Sprint Backlog Estimates Work remaining reporting during a Sprint updates the estimated number of hours required to complete a task. This should not be confused with time reporting, which is not part of. There are no mechanisms in for tracking the amount of time that a team works. Teams are measured by meeting goals, not by how many hours they take to meet the goal. is results oriented, not effort driven.
32 Practices -Sprint Thirty calendar day iteration Team builds functionality that includes product backlog and meets Sprint goal Team self-organizes to do work Team conforms to existing standards and conventions Abnormal termination of Sprint
33 Sprint If the Sprint requires >20% more work during the Sprint than was planned by the second day after the Sprint Planning meeting, it needs to plan better. If team members report the same item more than one day, they need to plan better and decompose the tasks to a greater level of granularity. The Product Backlog estimate is a mutually agreed to budget. If the team is going to exceed the budget, it needs to escalate the decision. Every member of the team is responsible for managing the team.
34 Sprint Abnormal Termination Sprints can be cancelled before the allotted thirty days are over Team can cancel Sprint if they feel they are unable to meet Sprint goal Management can cancel Sprint if external circumstances negate the value of the Sprint goal and If a Sprint is abnormally terminated, the next step is to conduct a new Sprint planning meeting, where the reason for the termination is reviewed.
35 Daily s Daily 15 minute status meeting Same place and time every day Meeting room Chickens and pigs Three questions 1. What have you done since last meeting? 2. What will you do before next meeting? 3. What is in your way? Impediments and Decisions
36 Task Reporting
37 What Is Being Made Visible? When a Team member says done, what does that mean? Code adheres to standards, is clean, has been refactored, has been unit tested, has been checked in, has been built, and has had a suite of unit tests applied to it Development environment for this to happen requires source code library, coding standards, automated build facility, and unit test harness
38 Sprint Review Meeting
39 What Is Being Made Visible? When the Team says done, what does that mean? Maintaining trust with customer by not hiding undone work. Functionality has been code reviewed, functionality has been integrated and built, acceptance tests have been run, and documentation has been created. QA environment for this has automated acceptance testing tools.
40 Sprint Retrospective Process improvement at end of every Sprint Facilitated by Master What went well, what could be improved. Master prioritizes based on team direction Team devises solution to most vexing problem
41 Report Progress Planned product backlog and releases. Revised product backlog and releases. Complete analysis of any changes in backlog, priorities, estimates Analysis of productivity Progress toward release Actions to improve
42 Managing a Release Business determines when a release is needed, what functionality it must contain, and what is an acceptable level of quality and cost Development determines how long it takes to build the release. Development creates preliminary estimates Development refines the estimates as priority increases Development selects the product backlog for development, each Sprint. Business focuses on business value derived from the release.
43 Compliance with CMM Software Framework Level Key Practice Area Requirements management Software project planning Software project tracking and oversight Rating 2 Software subcontract management 2 2 Software quality assurance Software configuration management 3 3 Organization process focus Organization process definition 3 3 Training program Integrated software management 3 Software product engineering 3 3 Intergroup coordination Peer review
44 Project QuickStart Participants: Team, Product Owner, Master, chickens, teacher Agenda Teach concepts, theory, practices Present project vision, goals, timelines Teach Sprint planning Define Product Backlog for at least three months Brainstorm about overcoming impediments Brainstorm about Product Backlog for next Sprint team commits Team defines Sprint Backlog Teach daily, Sprint review, Sprint signature, and management Discuss engineering tools and practices
45 Recommended Readings Agile Project Management with, Ken Schwaber 2004 User Stories Applied, Mike Cohn,Pearson Education, 2004 Extreme Programming Explained, Kent Beck, Addison Wessley, 2000 American Ground, William Langewiesche, North Point Press, 2002 The Blind Men and the Elephant: Mastering Project Work, David Schmaltz, Berrett-Koehler Publishers;, March 2003 Corps Business, David Freedman, HarperCollins, 2000 Industrial Dynamics, Jay W. Forrester, MIT Press, 1961 Complexity and Management, Ralph D. Stacey, Routledge, 2000 Project Retrospectives, Norman Kerth, Dorset House, 2001 The Art of Focused Conversation, Brian Stanfield, New Society Publishers, 2000 The Alphabet Versus the Goddess, Leonard Shlain, Viking, 1998 The Remembered Present, Gerald Edelman, Basic Books, 1989 The Dreams of Reason, Heinz Pagels, Simon and Schuster, 1988 The Knowledge Creating Company, Nonaka and Takeuchi, Oxford University Press, 1995 The Pragmatic Programmer, Hunt and Thomas, Addison Wesley, 2001 Lean Software Development, Poppendieck and Poppendieck, Addison Wesley, 2003 The Capability Maturity Model, Paulk et al, Addison Wesley, 1994 Agile & Iterative Development, Craig Larman, Pearson Education, 2004
46 Resources The Alliance: (www.scrumalliance.org) Control Chaos: (www.controlchaos.org) Agile Alliance: (www.agilealliance.org) Trainings by scrumeducation: (www.scrumeducation.com)
Utvecklar människor och mjukvara Agile software development using Scrum - in real life Citerus Myself Founded 1996 in Uppsala, HQ in Uppsala, office in Stockholm Offers consultancy with the whole spectrum
Getting Agile with Scrum Mike Cohn Mountain Goat Software email@example.com 1 Mike Cohn - background 2 We re losing the relay race The relay race approach to product development may conflict
Using SCRUM as a Test Management method ASTA conference 2007 Seoul, Korea Presented by Klaus Olsen Softwaretest.dk & Klaus Olsen 2007. Agenda Introduction Scrum Agile Estimation Test management Klaus Olsen,
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
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
An ISC Introduction to Agile and Scrum Larissa Shapiro All Hands, 2010 Scrum? Rugby? Is this an HR policy violation? What is she on about?? The relay race approach to product development may conflict with
Scrum It Depends on Common Sense http://www.controlchaos.com http://www.agilealliance.org Ken.firstname.lastname@example.org Advanced Development Methods 2003 All Rights Reserved 1 Read this Project Background Today
Learn. Inspect. Adapt: An Overview of Agile Project Delivery Doug Rosenberg and Kara Silva June 19, 2008 Paper Airplanes! The Agile Manifesto We are uncovering better ways of developing software by doing
An Introduction to Agile SCRUM Methodology Presumptions The audience is well aware of traditional software development methodologies like Waterfall Model, Iterative models, etc. Agenda Introduction What
The Scrum Guide The Definitive Guide to Scrum: Rules of the Game TABLE OF CONTENTS Purpose of the Scrum Guide...3 Scrum Overview...3 Scrum Framework...3 Scrum Theory...4 Scrum...5 The Scrum Team...5 The
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
innovel SCRUM Study Guide for Scrum Alliance Certified Scrummaster (CSM) Online Assessment. Version 2013 Authored by Jeff Sutherland and Ken Schwaber Table of Contents Purpose of the Scrum Guide... 3 Definition
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
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
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
Sprint to Your Market With Agile An Introduction to Agile Software Development Evan Leonard Senior Program Manager October 7, 2013 What Is Agile? Agile is a broad movement that is becoming the new industry
Agile and Scrum Concepts for Business Analysts Craig Fox Vice President, Senior Business Analyst Bessemer Trust Certified Scrum Product Owner (CSPO) @SR_BIZ_Analyst https://www.facebook.com/businessanalystprofessionals
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
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
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 Software Development with Scrum Jeff Sutherland Gabrielle Benefield Agenda Introduction Overview of Methodologies Exercise; empirical learning Agile Manifesto Agile Values History of Scrum Exercise:
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
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
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
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
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
February 2010 Scrum: Developed and sustained by Ken Schwaber and Jeff Sutherland Acknowledgements General Scrum is based on industry-accepted best practices, used and proven for decades. It is then set
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
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,
SCRUM Guidelines Senior Project Computer Science (Draft) SCRUM: A process framework that consists of a Scrum Team and their associated roles, events, artifacts and rules. The rules bind together the events,
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
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
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
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
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
Agile Testing and the Role of the Agile Tester Declan Whelan email@example.com This presentation is licensed under a Creative Commons Attribution 2.5 License, which means you can share and adapt it,
User Stories Done Right: Requirements Jeff Sutherland, Ph.D. Co-Creator Creator of Scrum http://jeffsutherland.com jeffsutherland.com/scrum For those of you doing Scrum You know who the product owner is
Lean and Agile Development With Scrum (Part 1) Lucio Davide Spano firstname.lastname@example.org email@example.com 3 May 2012 Agile Programming http://www.dilbert.com Traditional Software Development Waterfall
How can I be agile and still satisfy the auditors? Welcome & Introductions Steve Ropa Steven.firstname.lastname@example.org Agile Coach Certified Scrum Master Certified Scrum Product Owner 19 years software development
Using Scrum to Streamline Web Applications Development and Improve Transparency Michelle Frisque September 2010 OVERVIEW! Background! The problem! The proposed solutions:! Creation of Web Committee! Implementing
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
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
Scrum in five minutes Scrum and agile methods are hot topics these days A simple method for the management of complex projects... Older methods focus on staying on track; Scrum is aimed at delivering business
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
INF1581: Process Improvement and Agile Methods in Systems Development 01 nov. 2016 Scrum and Large scale Scrum email: email@example.com INF5181->Large Scale Scrum - Yngve Lindsjørn 1 Structure of Lecture
Introduction to Scrum Based on: Certified Scrum Master Ken Schwaber Certified Scrum Master Bas Vodde Scaling Agile & Lean Bas Vodde, Craig Larman Overview 2 Start with Plan and all requirements Predictive
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 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
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
Certified ScrumMaster Workshop Learn, understand, and execute on the three overarching principles behind Scrum: iterative development, self-management, and visibility. Even projects that have solid, well-defined
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
Selling Agile at Your Company Presented by William F. Nazzaro Hosted by Dave Bieg, Executive Vice President About DevelopMentor DevelopMentor provides solutions for all professionals involved in the lifecycle
Selecting a Development Process Mike Cohn Founder Mountain Goat Software Boulder, CO firstname.lastname@example.org Agenda The processes Team Software Process Scrum Extreme Programming The Unified Process
Jan Marek Jan.Marek@ca. com CA Technologies Session S601 Introducing Agile development methodologies to mainframe development teams Agenda Introduce Agile software development methodologies Scrum overview
Agile and Secure: Can We Be Both? OWASP AppSec Seattle Oct 2006 Keith Landrus Director of Technology Denim Group Ltd. email@example.com (210) 572-4400 Copyright 2006 - The OWASP Foundation Permission
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
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
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
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
Question 1 of 30 Who is required to attend the Daily Scrum? Correct answer: You chose: The Development Team. B) The Scrum team. C) The Development Team and Scrum Master. D) The Development Team and Product
Question 1 of 30 Scrum Master is a "management" position? Correct answer: You chose: True B) False The Scrum Master manages the Scrum process. If the Scrum Master is not a management position, he or she
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
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
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
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
An Example Checklist for ScrumMasters Michael James (firstname.lastname@example.org) 14 September 2007 (Revised 24 July 2012) A Full Time Facilitator? An adequate ScrumMaster can handle two or three teams at a time.
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
Agile Software Development in the Large GI-Vortrag Braunschweig Jutta Eckstein Nicolai Josuttis What Does Large Mean? Large in... scope time people money risks We focus on Large Teams which implies everything
BIO PRESENTATION T14 6/21/2007 1:30:00 PM "TIMELINES, ARTIFACTS AND OWNERS IN AGILE PROJECTS" Hubert Smits Rally Software Development Better Software Conference & EXPO June 18-21, 2007 Las Vegas, NV USA
Certified ScrumMaster Workshop AG09; 2 Days, Instructor-led Course Description In this ScrumMaster Certification training course you will learn, understand and execute on the three overarching principles
Scrum In A Nutshell Scrum is about Teams producing Results in an agile way. Scrum Teams achieve results anyway they can by using a simple set of rules to guide effort. We will describe scrum as a simple
Agile Software Project Management with Scrum Viljan Mahnic, Slavko Drnovscek University of Ljubljana, Faculty of Computer and Information Science Trzaska 25, SI-1000 Ljubljana, Slovenia email@example.com,
Getting Agile with Scrum Mike Cohn 6 June 2012 We re losing the relay race The relay race approach to product tries to go the distance as a unit, passing the competitive requirements. Hirotaka Takeuchi
Introduction to Agile and Scrum Bob Schommer, CSP, PMP, MCTS Senior Project Manager Skyline Technologies, Inc. PMI Northeast Wisconsin Chapter May 3, 2011 About Skyline Technologies Microsoft Gold Certified
VSR EDU Distributed and Self-organizingComputer Systems Prof. Gaedke Current Trends in Web Engineering Prof. Dr.-Ing. Martin Gaedke Technische Universität Chemnitz Fakultät für Informatik Verteilte und
Facilitation Foundations Improving the Quality of Agile Meetings V. Lee Henson CST 1 Improving the Quality of Agile Meetings 2 V. Lee Henson CST Certified Scrum Trainer ADDIE Training Professional Agile
Agile Software Construction Beatrice Åkerblom firstname.lastname@example.org Course Council? First Class? Scrum What is Scrum? Scrum -- Introduction! Scrum is a simple framework for project management on complex projects!
Scrum and CMMI: A High level assessment of compatibility Srinivas Chillara 1 and Pete Deemer 2 Abstract: This article s purpose is to assess the compatibility of Scrum with CMMI and also provide a base
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
Introduction to for Managers and Executives goodagile> Certified Training and Consulting in India and Asia www.goodagile.com The Problems Many Companies Face Time-to-market for products is too long Project
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