Not your average bacon and eggs

Slides:



Advertisements
Similar presentations
Agile Development Primer – Using Roundtable TSMS in an Agile Shop Michael G. Solomon Solomon Consulting Inc.
Advertisements

Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.
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.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
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.
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
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
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.
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.
SCRUM Not your average bacon and eggs. The Basics Product Backlog Sprint Backlogs Sprints – The Daily Scrum – Burn-down chart Sprint Retrospective.
Scrum Practices Sprint-2. Agenda Scrum Master Product Backlog Scrum Teams Daily Scrum Meeting Sprint Planning Meeting Sprint Sprint Review.
Software Project Management Team 04 – K15T2. Content Summarizing your view on “Software development process”. Answer 3 question: ◦ What is Software Development.
Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.
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.
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?
Software Quality Assurance Chip Ene, February 14, 2015.
Created By:-
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?
Agile Scrum Development Carter Jasinski. Outline ● Introduction ● Roles ● Artifacts ● Sprints ● Uses.
Agile Processes: Scrum
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Project Management Methodology Scrum Overview
Scrum.
Scrum and TargetProcess
Wael Ellithy, Ph.D. Arx ICT
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
Agile Scrum Management
Agile Development -- an overview
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
COMP 135: Human-Computer Interface Design
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
CS 577b: Software Engineering II
Project & Program Governance
Chapter 3: The Project Management Process Groups: A Case Study
Agile Development -- an overview
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
Scrum MODULE 3 – Part 3.
Johanna Rothman Agile Team Measurements Chapter 12
Teaching slides Chapter 1.
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
© University of Liverpool
Tools and Techniques for Agile Project Management
Scrum Science NGSS: Engineering, Technology, Applications of Science
Adjective: Able to move quickly and easily. Principles and Values
Scrum Science NGSS: Engineering, Technology, Applications of Science
Taking it to the next level
Scrum: Daily Stand Up Meeting
Sprints.
Business Agile 101 Learn the basics of the agile methodology and how you and your team can take steps to apply it to your workflow.
Agile, Scrum and CMMI Methodologies
Presentation transcript:

Not your average bacon and eggs 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 Cons 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.