SCRUM Not your average bacon and eggs. The Basics Product Backlog Sprint Backlogs Sprints – The Daily Scrum – Burn-down chart Sprint Retrospective.

Slides:



Advertisements
Similar presentations
Team Development with Microsoft Scrum 1.0 Doncho Angelov Developer Evangelist Microsoft Bulgaria.
Advertisements

Agile Development Primer – Using Roundtable TSMS in an Agile Shop Michael G. Solomon Solomon Consulting Inc.
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
1 1  Test the Scrum Knowledge of your team.  Play by the rules of Jeopardy® ◦ Play in two teams ◦ Assign a score keeper ◦ All answers have to be in.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
RTC Agile Planning Component
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Scrum in 30 minutes! Oddly, a 45-minute presentation by Carl Chatfield Content Project Manager, Microsoft Puget Sound MPUG September 2009.
Chaos and Collaboration A Successful Adoption of Scrum by a Government Department Pete George George Training & Development Ltd
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
© Timothy Korson Page 1 Scrum by Dr. Korson For CPTR 209 Software Engineering Version
Scrum introduction XP Days Agenda Introduction The Scrum process – roles, ceremonies and artifacts Backlog management Conclusions and questions.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Agile development By Sam Chamberlain. First a bit of history..
The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team.
Agile Design and SCRUM Brent M. Dingle, Ph.D. “For the last few centuries, … science has been attempting to break matter down into ever smaller bits, in.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
1 Agile Methodology & Programming Ric Holt July 2009.
What is Scrum Process? Where is it used? How is it better?
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Agile Adoption GMAS Product / Practice Teams PMO Meeting – May 2014.
Page 1/8 Waterfall  Agile  Scrum Development department.
SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.
Scrum Practices Sprint-2. Agenda Scrum Master Product Backlog Scrum Teams Daily Scrum Meeting Sprint Planning Meeting Sprint Sprint Review.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
Software Project Management Team 04 – K15T2. Content Summarizing your view on “Software development process”. Answer 3 question: ◦ What is Software Development.
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
Giving order to the chaos of agile Presented by Matt Campo CSC 490 Fall 2015.
SCRUM.
Using Scrum to Improve Teamwork, Communication, Quality and Speed
Lecture 5 17/9/15. What is Scrum? Scrum is one of the leading agile software development processes Agile framework for completing complex projects. Originally.
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
Over Contract negotiation over Processes and tools over Comprehensive documentation overFollowing a plan over.
Introduction to Agile. Introduction Who is this guy?
1 Development with Agile methodology Scrum Lifecycle DEVELOPMENT PROCESS IN DROISYS INC.
Created By:-
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(3)
Copyright © Curt Hill Scrum Software Development Paradigms What is a Scrum?
Project Management with VSTS
Scrum.
Wael Ellithy, Ph.D. Arx ICT
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
Agile Scrum Management
Agile Development -- an overview
Not your average bacon and eggs
COMP 135: Human-Computer Interface Design
Agile Development -- an overview
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
Scrum MODULE 3 – Part 3.
Johanna Rothman Agile Team Measurements Chapter 12
SCRUM from product owner point of view
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
© University of Liverpool
Scrum Overview.
Adjective: Able to move quickly and easily. Principles and Values
Scrum Science NGSS: Engineering, Technology, Applications of Science
Scrum: Daily Stand Up Meeting
Agile, Scrum and CMMI Methodologies
Presentation transcript:

SCRUM Not your average bacon and eggs

The Basics Product Backlog Sprint Backlogs Sprints – The Daily Scrum – Burn-down chart Sprint Retrospective

The Players The Scrum Team – Consists of five to nine people – No specific roles Still allows for experts – Primary tasks involve problem solving and design

The Players The Scrum Master – More the role of a coach – Daily Scrum Keeps Scrum team focused Provides Scrum team with most beneficial circumstances possible – Sprint Retrospective Helps team evaluate progress and accomplishments Motivates team for next Sprint

The Players The Product Owner – Voice of the customer – Maintains a business perspective – Responsible for the product backlog

The Process The Product Backlog – Contains a list of prioritized goals May include upgrades, bug fixes, or the next steps in development – Can be broken down into segments This should create business value This should also allow it to be sub-deliverable

The Process The Daily Scrum – Consistent time every day – Involves Scrum Master and Scrum Team “What has been accomplished since we last met?” “What will be accomplished between now and our next meeting?” “Is there anything standing in our way?” – No one else is allowed to talk Bacon and eggs

The Process The Sprint – Consists of 30 days Often non-negotiable – Series of predetermined goals Specified by the Sprint backlog – Uses a burn-down chart is used to display progress – Concludes with Sprint Retrospective Allows team to demonstrate product A good time for evaluation and motivation for the next Sprint

Pros and Cons Pros – The small size allows for agility – The Sprints allow for members to be remain focused and motivated – Team members can put their strengths to use without being confined to specific roles Cons – Unorthodox in that there is no project manager – There is difficultly in overcoming inertia – Strict timing can sometimes be harmful

Conclusions Scrum has been successfully integrated into companies such as IBM, Microsoft, and Xerox. Scrum works best when the numbers relating to the team size, Sprint time, and overall project development time are reasonable. Its strongest aspect is continuous communication among the team members and the customers.