How to Adopt Scrum: A Better Approach to Project Management
|
|
- Flora Freeman
- 7 years ago
- Views:
Transcription
1 This article originally appeared on eweek on Friday, November 20, To access it online, visit: T-Management/How-to- Adopt-Scrum-A-Better- Approach-to-Project- Management/ How to Adopt Scrum: A Better Approach to Project Management By Jimi Fosdick When development companies first consider adopting Scrum, there's often confusion about what Scrum is and how to get started. Transforming a company with Scrum requires more than adopting its language and mechanics. Following its process and filling its roles is just one condition for real, sustainable change. The challenge is not only finding the right people to fill Scrum s roles, but embracing the underlying values that enable Scrum's benefits. Here, Knowledge Center contributor Jimi Fosdick explains how to start doing Scrum in your company. The best way for organizations to get started with Scrum is for them to first develop a strong understanding of Scrum's language and mechanics. Once these basic aspects of the Scrum framework are understood, the hard work of enacting change and internalizing the framework's values can begin. What follows is an introduction to Scrum's roles, artifacts and meetings, as well as advice for how organizations can successfully acclimate to a new approach to project management. After all, the language and mechanics of Scrum are quite simple, but its implementation is considerably more difficult. The Scrum Roles In Scrum, products are built incrementally over a series of consecutive development iterations called "Sprints." Scrum defines three roles that are responsible for managing both the process and the product development effort: Product Owner, ScrumMaster and the Scrum Team. When transitioning from traditional project management methods, it is important that individuals are chosen for the Scrum roles based on inclination, temperament, and skills not their position within the corporate hierarchy. Forcing someone into a role for which they are poorly suited or lack personal interest is a recipe for failure. Let's look at each of these roles:
2 1. The Product Owner According to Scrum co-founder Ken Schwaber, the Product Owner is "the person who is officially responsible for the project." Responsibilities include: - Defining product features - Understanding business/stakeholder needs - Prioritizing feature delivery based on stakeholder needs - Arbitrating requirements issues - Defining development priorities at the beginning of each Sprint - Negotiating acceptance criteria for features with the Scrum Team - Accepting or rejecting results of each cycle - Planning releases The Product Owner decides which features will be built into a product and the relative priority of each item. Moreover, the Product Owner must be highly attuned to the value generated by these features to ensure high-value features are delivered as early as possible to encourage feedback that leads to maximum ROI. 2. The ScrumMaster The ScrumMaster is responsible for the success of the process and the productivity and health of the Scrum Team. According to Schwaber, the "ScrumMaster is responsible for the success of Scrum." Further, the "ScrumMaster is responsible for ensuring that Scrum values, practices and rules are enacted and enforced. The ScrumMaster is the driving force behind all of the Scrum practices." Responsibilities include: - Keeping the process moving - "Enforcing" the Scrum framework - Facilitating and ensuring full-team involvement in all Scrum's meetings - Keeping everything visible - Communicating and sharing information to the larger organization - Shielding the team from external interference - Helping surface and remove obstacles impeding the Scrum Team from achieving its Sprint goals - Advocating improved practices - Tracking progress and posting it visibly Good ScrumMasters spend considerable time helping the rest of the organization understand Scrum, including the Product Owner.
3 It is important to understand that the ScrumMaster has no authority and is not a manager of people or projects. In addition, the ScrumMaster doesn't assign tasks to team members or monitor individual team member performance. Rather, the ScrumMaster must understand he or she is not "in charge" of anything. The role is one of "servant leadership" which relies on personal persuasiveness rather than organizational authority. In short, they serve the team by reminding them about the rules of the Scrum process; ultimately, it is up to the Scrum Team to observe those rules. 3. The Scrum Team The Scrum Team is comprised of about seven (plus or minus two) team members. Scrum advocates cross-functionality to allow a single team to accomplish development goals. Responsibilities include: - Estimating effort to complete Product Backlog Items - Committing to what it thinks it can accomplish each Sprint - Managing development of product functionality - Building Business Value - Defining its work (who does what and how) - Building and maintaining its schedule for the Sprint - Negotiating scope and acceptance criteria for Sprint goals - Anything required to turn a stakeholder's request into functional product One challenge for organizations that adopt Scrum is allowing teams to self-manage and self-organize. Often, existing organizational structures directly conflict with giving the team the autonomy required to accomplish its goals. Such organizations must actively shift from a parent/child relationship to a peer/peer relationship between management and "staff." This is where an effective and experienced ScrumMaster can play a crucial role in facilitating a smooth transition. Scrum Ceremonies and Artifacts The Scrum process itself prescribes only four meetings: Sprint Planning, the Daily Scrum, Sprint Review, and Sprint Retrospective. In addition, Scrum advocates face-to-face collaboration among team members and with various stakeholders. The planning artifacts include the Product Backlog, the Sprint Backlog, as well as the Product (or Release) and Sprint Burndowns for tracking progress. The Product Backlog
4 In the simplest terms, the Product Backlog is a list of features, functionality, technology and issues. The Product Backlog is: 1. Emergent: At any given time, the Backlog is only partially complete; additional features are added as they are discovered and features that are determined to be low-value are removed. 2. Prioritized: By definition, every item in the Backlog has a priority determined by its position in the list, with the highest priority backlog items appearing at the top. 3. Estimated: Each item in the Backlog is estimated by the people doing to work in terms of effort. There is one Product Backlog for multiple teams, which is maintained and posted visibly. Anyone can contribute to it but only the Product Owner determines priority. Very often, the Product Backlog is derived from a business plan or vision statement. Sprint Planning Each Sprint which is never longer than 30 calendar days begins with a Sprint Planning Meeting. This meeting is "timeboxed" at eight hours. (Timeboxing is an essential concept in Scrum, in which clear, rigid deadlines are set for most activities.) During Sprint planning, the team and the Product Owner negotiate the portion of the Product Backlog the team will attempt to deliver by the end of the Sprint, as well as a higher level "Sprint goal," describing the purpose of the Sprint. The Sprint goal(s) should be met, even if the team cannot complete all the selected Backlog items. Immediately after selecting Backlog items and agreeing on a Sprint goal, the team, either with or without the Product Owner present, decomposes the selected Product Backlog into constituent tasks. This detailed list of tasks is called the Sprint Backlog and serves as the team s plan for the next iteration. The Sprint Backlog The Sprint Backlog includes all the tasks necessary to turn the Product Backlog into working product functionality. Any team member can add, delete or change the Sprint Backlog as work for the Sprint emerges. On average, tasks should represent one day of work each; those that require more than two days should be broken down into
5 separate tasks. During the Sprint, team members volunteer for tasks they are not assigned to them and work remaining is updated daily. The Daily Scrum As the name implies, the Daily Scrum occurs each day at the same time. Only team members must attend and participate, but anyone is free to observe. During the Daily Scrum, team members discuss progress toward the current Sprint's goal using three questions: 1. What did I do since the last Daily Scrum? 2. What am I doing until the next Daily Scrum? 3. What are my impediments? There is the risk that the Daily Scrum will become a perfunctory (and low-value) status report if the ScrumMaster doesn't encourage active discussion. The ScrumMaster should encourage the team to talk to each other (rather than report to just the ScrumMaster) and use whatever techniques are appropriate to keep everyone engaged. The Sprint Review The Sprint Review occurs without exception on the last day of the Sprint. Here, the Scrum Team and Product Owner have an opportunity to reflect on progress toward current release goals. It also represents another "inspection point" in Scrum's ongoing inspect-and-adapt cycles. It is not a milestone or deliverable, although what is being inspected probably constitutes both. During the review, the team demonstrates the functionality developed and the Product Owner accepts or rejects the results based on previously established acceptance criteria. In addition, the team and Product Owner, with the ScrumMaster facilitating, review progress to date and adjust plans in light of emerging conditions. The Sprint Retrospective The Sprint Retrospective is the last Scrum meeting, concluding every Sprint. It is an opportunity to reflect on the quality and effectiveness of the team's processes and propose adjustments. It occurs immediately after the Sprint Review and focuses on strategies for continuous improvement. It is important that the team reflects on how it s been working so that it can implement improvements going forward.
6 A Final Thought Transforming an organization with Scrum is much more than just about changing people's titles and renaming meetings. The challenge involves literally learning to look at how work gets done differently. It's a radical shift in considering how work is managed and one that will be necessarily disruptive, but the results Scrum yields will be equally radical. Jimi Fosdick is a Certified Scrum Trainer at Danube Technologies. Jimi conducts dozens of public courses around the world each year, helping organizations to surface dysfunction and improve processes through Scrum. Before joining Danube, Jimi spent four years advocating agile approaches to project management first as a program and project manager, and later as an independent agile and Scrum consultant. During this time, Jimi worked with companies such as CIBER, Razorfish, MTV Networks and Microsoft, helping them transform to more agile ways of working using Scrum. Prior to these consulting engagements, Jimi spent a decade working in various capacities in software, including as a program manager of software product development and solutions architecture at the Riverside Publishing Company and as a senior staff developer at Polycom. Jimi is a PMI-certified PMP and received his MBA in Project Management from Keller Graduate School of Management. As an undergraduate, Jimi studied mathematics and computer science at Loyola University. He can be reached at jfosdick@danube.com.
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
More informationCertified 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
More informationCertified 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
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 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 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 informationT14 "TIMELINES, ARTIFACTS AND OWNERS IN AGILE PROJECTS" Hubert Smits Rally Software Development BIO PRESENTATION 6/21/2007 1:30:00 PM
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
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 informationACP Exam Prep Plus Desk Reference including the Project Management Agile Body of Knowledge TM (PMABOK TM )
ACP Exam Prep Plus Desk Reference including the Project Management Agile Body of Knowledge TM (PMABOK TM ) Contents Homework Assignment for 2 PDUs... 1 Chapter Close-Out... 2 Terminology Matching Exercise...
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 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 informationManaging Agile Projects in TestTrack GUIDE
Managing Agile Projects in TestTrack GUIDE Table of Contents Introduction...1 Automatic Traceability...2 Setting Up TestTrack for Agile...6 Plan Your Folder Structure... 10 Building Your Product Backlog...
More informationGetting 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 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 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 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 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 informationScrum In 10 Slides. Inspect & Adapt
Scrum In 10 Slides Inspect & Adapt Why Scrum? 52.7% projects cost 189% of their original estimates 60% of functionality delivered is rarely or never used 80% of the value comes from 20% of the functionality
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 informationThe 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)
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 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 Team Roles Product Owner & ScrumMaster. Brian Adkins Rick Smith
Agile Team Roles Product Owner & ScrumMaster Brian Adkins Rick Smith Agenda Scrum & Team Roles Overview Product Owner ScrumMaster Existing Roles Scrum Teams Optimally about 7 people Sponsor Stakeholders
More informationNexus Guide. The Definitive Guide to Nexus: The exoskeleton of scaled Scrum development. Developed and sustained by Ken Schwaber and Scrum.
Nexus Guide The Definitive Guide to Nexus: The exoskeleton of scaled Scrum development Developed and sustained by Ken Schwaber and Scrum.org August 2015 Table of Contents Nexus Overview... 2 Purpose of
More informationScrum. 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
More informationAGILE - QUICK GUIDE AGILE - PRIMER
AGILE - QUICK GUIDE http://www.tutorialspoint.com/agile/agile_quick_guide.htm Copyright tutorialspoint.com AGILE - PRIMER Agile is a software development methodology to build a software incrementally using
More informationScrum for Project Managers
Scrum for Project Managers Examining the Project Manager s role in a successful Scrum organization Angela Druckman Certified Scrum Trainer adruckman@collab.net Presentation Overview Scrum in a perfect
More informationFREE ONLINE EDITION. (non-printable free online version) Brought to you courtesy of Sprint-IT &
FREE ONLINE EDITION (non-printable free online version) If you like the book, please support the author & InfoQ by purchasing the printed version: www.sprint-it.de/scrum-checklists (only 19,90 euro) Brought
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 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 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 informationScrum. in five minutes
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
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 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 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 informationChapter 6. Iteration 0: Preparing for the First Iteration
Chapter 6. Iteration 0: Preparing for the First Iteration People only see what they are prepared to see. Ralph Waldo Emerson There are no secrets to success. It is the result of preparation, hard work,
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 informationScrumMaster 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
More informationDevelopment phase 1.3. isupport. Project Name: isupport Date: 24-6-2015 Release: 1.3. Document Name: HCCH isupport Development phase project team 1
cross-border recovery of maintenance obligations pour le recouvrement transfrontière des obligations alimentaires Development phase Project Name: Date: 24-6-2015 Release: 1.3 Authors: Brigitte Voerman
More informationScrum. Speaker: Dan Mezick Email: info@newtechusa.com. URL: NewTechUSA.com. http://www.newtechusa.com Copyright 2002: All rights reserved
3 Roles, 3 Ceremonies, 3 Artifacts, 3 Best Practices Scrum Speaker: Dan Mezick Email: info@newtechusa.com Phone: 203-234-1404 URL: NewTechUSA.com Scrum s THREE ROLES The actors in Scrum: Product Owner,
More informationAgile Methods for Analysis
Agile Methods for Analysis Lightweight Concepts for Team-Based Projects Sebastian Neubert CERN PH-LBD Sebastian Neubert Agile Analysis 1/22 Introduction: Data Analysis as a Continuous Improvement Loop
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 informationEstablishing and Maintaining Top to Bottom Transparency Using the Meta-Scrum
ARTICLE Establishing and Maintaining Top to Bottom Transparency Using the Meta-Scrum by Brent Barton Agile Journal Oct. 6, 2007 Agile processes and practices have gained enough attention that both IT businesses
More informationSmartBear Software Pragmatic Agile Development (PAD) Conceptual Framework
Pragmatic Agile Development (PAD) Conceptual Framework This document describes the Pragmatic Agile Development framework, a Scrum based development process. SmartBear Software 3/10/2010 Pragmatic Agile
More informationNo 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
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 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 informationUsing Scrum to Streamline Web Applications Development and Improve Transparency. Michelle Frisque
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
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 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 informationOverview of Scrum. Scrum Flow for one Sprint. 2015 SCRUMstudy.com. All Rights Reserved. Daily Standup. Release Planning Schedule. Create.
Overview of Scrum Scrum is the most popular Agile framework. It is an adaptive, iterative, fast, flexible, and effective method designed to deliver significant value quickly and throughout a project. Scrum
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 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 informationWE ARE FOCUSED ON HELPING OUR CLIENTS WORK SMARTER AND MORE EFFICIENTLY SO THAT TOGETHER, WE CAN EMPOWER PEOPLE TO DELIVER GREAT RESULTS.
WE ARE FOCUSED ON HELPING OUR CLIENTS WORK SMARTER AND MORE EFFICIENTLY SO THAT TOGETHER, WE CAN EMPOWER PEOPLE TO DELIVER GREAT RESULTS. We believe that people working towards common goals are capable
More informationGlobal Business Services, GBS. Scrum and Kanban. Processer & IT nord seminar 5v3. Gitte Klitgaard Hansen, IBM
Scrum and Kanban Processer & IT nord seminar 5v3 Gitte Klitgaard Hansen, IBM Agenda Who am I? My background in scrum and agile Basics of scrum Basics of kanban When do you use scrum and kanban? 2 Who am
More informationIntroduction to Scrum
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
More informationEXIN Agile Scrum Foundation. Sample Exam
EXIN Agile Scrum Foundation Sample Exam Edition June 2016 Copyright 2016 EXIN All rights reserved. No part of this publication may be published, reproduced, copied or stored in a data processing system
More informationAgile Software Project Management with Scrum
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 viljan.mahnic@fri.uni-lj.si,
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 informationThe Agile Service Management Guide. By Jayne Gordon Groll
The Agile Service Management Guide By Jayne Gordon Groll Sources and Acknowledgements The Scrum Guide by Ken Schwaber and Jeff Sutherland, July, 2013 The ITSM Process Design Guide by Donna Knapp, ISBN:
More informationFebruary 2010. Scrum: Developed and sustained by Ken Schwaber and Jeff Sutherland
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
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 informationStrategic Vision and Scrum: Looking Beyond the Next Sprint. Jimi Fosdick Certified Scrum Trainer and Scrum Mentor
Strategic Vision and Scrum: Looking Beyond the Next Sprint Jimi Fosdick Certified Scrum Trainer and Scrum Mentor Abstract When organizations adopt an agile approach like Scrum to product development oftentimes
More informationExtreme programming (XP) is an engineering methodology consisting of practices that ensure top-quality, focused code. XP begins with four values:
Scrum with XP By Kane Mar, Ken Schwaber. Introduction Scrum and extreme programming (XP) are both Agile methodologies. We've heard controversy regarding the value of each, with people familiar with each
More informationThe Agile PMO. Contents. Kevin Thompson, Ph.D., PMP, CSP Agile Practice Lead cprime, Inc. 4100 E. Third Avenue, Suite 205 Foster City, CA 94404
The Agile PMO Kevin Thompson, Ph.D., PMP, CSP Agile Practice Lead cprime, Inc. 4100 E. Third Avenue, Suite 205 Foster City, CA 94404 Kevin.thompson@cprime.com Abstract The development of Agile processes
More information0. INTRODUCTION 1. SCRUM OVERVIEW
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
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 informationManaging a Project Using an Agile Approach and the PMBOK Guide
Managing a Project Using an Agile Approach and the PMBOK Guide Kathy Schwalbe, Ph.D. schwalbe@augsburg.edu Augsburg College Minneapolis, Minnesota September 25, 2012 Abstract This paper includes excerpts
More informationScaling Scrum Professionally using Nexus and Visual Studio Team Services
ALM Scaling Scrum Professionally using Nexus and Visual Studio Team Services If you have been using Scrum to develop products, you have probably found that the Scrum Guide only describes the core rules
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
Agile software development Syed Nisar Hussain Bukhari Scientist-B DOEACC centre Srinagar nisar.bukhari@gmail.com Abstract: The field of software development is open and dynamic. New approaches of software
More informationIntroduction to Scrum for Managers and Executives
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
More informationCertified ScrumMaster Workshop
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
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 informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 9 Agile Methodologies: Scrum 1 Scrum First mentioned as a development method in 1986, referring to a fast and flexible product development
More informationReferences: 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
More informationAgile Scrum Foundation Training
IMPROVEMENT BV Liskesweg 2A 6031 SE Nederweert www.improvement-services.nl info@improvement-services.nl tel: 06-55348117 Tools for Optimum Performance Agile Scrum Foundation Training ~ Scrum Master Sample
More informationScrum includes a social agreement to be empirical as a Team. What do you think an empirical agreement is?
Scrum Discussion Questions For the Facilitator These questions and subsequent discussion points are designed to help you and your Team more efficiently implement Scrum. The following are discussion points
More informationAgile 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
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 informationAgile Notetaker & Scrum Reference. Designed by Axosoft, the creators of OnTime the #1 selling scrum software.
Agile Notetaker & Scrum Reference Designed by Axosoft, the creators of OnTime the #1 selling scrum software. Scrum Diagram: Team Roles: roduct Owner: Is responsible for what goes into the product backlog
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 informationSESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization
SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization Secrets of a Scrum Master: Agile Practices for the Service Desk Donna Knapp Curriculum Development Manager, ITSM Academy
More informationIteration Planning. also called Iteration Kickoff
Agile Practices also called Iteration Kickoff Iteration Planning Purpose: Discuss detailed requirements of the stories to be built in the iteration. Review and refine the acceptance criteria for each story
More informationWould you like to have a process that unlocks ability to learn and produce faster?
Would you like to have a process that unlocks ability to learn and produce faster? Agile - your unfair advantage in the competition. BUILD LEARN MEASURE DEFINED MEASURABLE REPEATABLE COLLABORATIVE IMPROVABLE
More informationCreating a High Maturity Agile Implementation
Creating a High Maturity Agile Implementation Creating a High Maturity Agile Implementation www.qaiglobal.com 1 Copyright Notice 2015. Unless otherwise noted, these materials and the presentation of them
More informationScrum 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:
More informationMeasurement repository for Scrum-based software development process
Measurement repository for Scrum-based software development process VILJAN MAHNIC, NATASA ZABKAR Faculty of Computer and Information Science University of Ljubljana Trzaska 25, SI-1000 Ljubljana SLOVENIA
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 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 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 informationIMQS TECHNOLOGY AGILE METHODOLOGY
IMQS TECHNOLOGY AGILE METHODOLOGY OVERVIEW Agile software development refers to a group of software development methodologies that promotes development iterations, open collaboration, and process adaptability
More informationAgile Scrum and PMBOK Compatible or Contrary?
Agile Scrum and PMBOK Compatible or Contrary? Paul Despres PMI Emerald Coast Panama City Branch June 26, 2014 Meeting Overview Agenda Topics: Review Agile/Scrum Methods Review PMBOK Structure Demonstrate
More informationRISK 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
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 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 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 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 informationIs the Project Manager and Endangered Species? Roman Pichler
Is the Project Manager and Endangered Species? Roman Pichler About me Roman Pichler Consultant and Author Lean and Scrum Tel.: +44 (0) 7974 203772 roman.pichler@romanpichler.com www.romanpichler.com 2008
More informationIntroduction to Agile Practices
Introduction to Agile Practices Phyllis Marbach, INCOSE Agile Systems & Systems Engineering Working Group February 2, 2016 INCOSE INSIGHT July 2014 1 Current State of Intelligent Transportation Systems
More information