Www.rose-hulman.edu/~mutchler/gcer2012 David Mutchler Professor of Computer Science and Software Engineering Rose-Hulman Institute of Technology 5500 Wabash.

Slides:



Advertisements
Similar presentations
Basic SDLC Models.
Advertisements

Transition to Scrum Midway through a AAA Development Cycle: Lessons Learned Asbjoern Malte Soendergaard Development Manager Crytek GmbH.
Agile Development Primer – Using Roundtable TSMS in an Agile Shop Michael G. Solomon Solomon Consulting Inc.
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
Agile Development Chapter Extension 16. ce16-2 Study Questions Q1: Why is the SDLC losing credibility? Q2: What are the principles of agile development.
Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.
Project Strategies [A&N 1,2] Wishnu Prasetya. Managing a large software project Software Development Life Cycle (SDLC) Typical phases in : Planning, Requirement,
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.
Agile development By Sam Chamberlain. First a bit of history..
Agile Methods and Extreme Programming CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 23, 2007.
Software Development Overview CPSC 315 – Programming Studio Spring 2009.
An Agile View of Process
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
Agile Methodologies for Project Management By – Komal Mehta.
Dr. Tom WayCSC Software Processes CSC 4700 Software Engineering.
1 Agile Methodology & Programming Ric Holt July 2009.
Copyright 2008 Scott W. Ambler Agile Practices and Principles Survey 2008 Scott W. Ambler Michael.
Software Engineering Modern Approaches
Agile Programming Principles.
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib.
Project Workflow. How do you do it? -Discussion-
Chapter 5 애자일 개발 Agile Development
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
Agile Project Management. An Informed Decision It is not a snap decision whether to use an agile approach or not, just like flying or driving somewhere.
CS 5150 Software Engineering Lecture 3 Software Processes 2.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
CSE 436—Software Development Models Ron K. Cytron 10 October 2005.
CSE 436—Software Development Models Ron K. Cytron 16 October 2006.
IS3320 Developing and Using Management Information Systems Lecture 20: Project Management Rob Gleasure
Software Engineering (CSI 321) An Agile View of Process 1.
Sprint Plans and Burndown Charts David Millard | davidmillard.org.
Dr. Rob Hasker. What if every project used Scrum?  Why might Scrum not be perfect for every project? Hard to get the big picture Early choices may have.
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Testing and Evaluating Software Solutions Introduction.
Dr. Rob Hasker. Should every project use Scrum?  When might Scrum not be an appropriate model?  What are some of its limitations? Hard to get the big.
Software Engineering 2004 Jyrki Nummenmaa 1 Why new software methodologies The classic waterfall-model based techniques are strongly based on the.
Introduction to Agile. Introduction Who is this guy?
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Chapter 9 Planning. 222 Learning Objectives  clearly defining the project objective  developing a work breakdown structure  developing a network diagram.
Project Workflow.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Embedded Systems Software Engineering
Introduction to Agile Software Development
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
SCRUM the Schedule This presentation provides an introduction to:
Project Workflow.
Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Software Engineering (CSI 321)
Project Management and the Agile Manifesto
Decomposition.
How to Successfully Implement an Agile Project
Teaching slides Chapter 1.
Chapter 5 Planning
What is Scrum, and How Does It Relate to MS Project?
Scrum Overview.
Introduction to Agile Blue Ocean Workshops.
Practical Software Engineering
Adjective: Able to move quickly and easily. Principles and Values
Computer Science & Engineering Electrical Engineering
Chapter 3: Agile Software Processes
Presentation transcript:

David Mutchler Professor of Computer Science and Software Engineering Rose-Hulman Institute of Technology 5500 Wabash Ave. Terre Haute, IN (812)

Take-away (preview) Botball teams need Project Management But Project Management is hard! Current focus: Gantt Charts Waterfall processes Another way: Agile processes Simplified Scrum for Botball

What is Project Management? Henry Gantt ( ), the father of planning and control techniques Photo and diagram are from Wikipedia, Typical phases of an engineering project

Project Management in Botball – Gantt Chart

Waterfall Project Management The diagram is from Wikipedia, It was adapted from Managing the Development of Large Software Systems, by Winston W. Royce, 1970, /files/original_waterfall_paper_winston_royce.pdf. /files/original_waterfall_paper_winston_royce.pdf Building: Cars Software  Waterfall was incorporated in DOD standards like the one shown above,

Agile Project Management From and We follow these principles: … Deliver working software frequently … … Build projects around motivated individuals … … Working software is the primary measure of success … … Simplicity – the art of maximizing the amount of work not done – is essential … These sound like good fits for Botball!

Scrum Diagram adapted from Agile Software Development with Scrum by Schwaber and Beedle, 2001, taken from Each big cycle is called a Sprint. Each Sprint begins with planning what to deliver and ends with a working product.

Simple Scrum in Botball Generic Release Plan Sprint Beta Sprints 1, 2, 3, … Sprint Alpha Deliverables for each Sprint, see next slide  Team building  Staged Strategy Determine and assign Tasks to accomplish the deliverables for this Sprint Stand-up Meeting to adjust Tasks and assignments as needed Re-Plan for the next Sprint, based on what was learned from this Sprint Each Sprint: Robots score more points

A generic Release Plan for Botball Sprint Alpha: Plan for how to build the team Team rules: participation, decision-making, conflict-handling, … Sprint Beta: Staged Strategies for Seeding and Double-Elimination Sprint 1: Robots accomplish Stage 1 of Seeding Strategy Robots accomplish Stage 1 of Double-Elimination Strategy Sprints 2, 3, 4… Robots accomplish Stage 2… of Seeding Strategy Robots accomplish Stage 2… of Double-Elimination Strategy

After Sprint Beta: Sprint 1: Starts, leaves box, stops, moves over bumps on board and through turnstile, all very reliably. Sprint 2: Scores 12 x 10 = 120 points reliably by scoring 12 of 12 Tilapia. Sprint 3: Scores 180 additional points reliably by scoring 6 (or more) of 10 Kelp. Sprint 4: Scores 410 additional points reliably by scoring 7 (or more) of 10 polyps from opponent's side and 3 (or more) from our side into reefs and into MPA. Sprint 5: Scores TBD to TBD points reliably by scoring TBD. This and the next slides show an example of how the Release Plan might evolve. Only the Seeding Strategy is shown.

After Sprint 1: Accomplished: Starts, leaves box, stops, moves over bumps on board and through turnstile, all very reliably. Sprint 2: Scores 12 x 6 = 72 points reliably by scoring at least 6 of 12 Tilapia. Sprint 3: Scores 60 additional points reliably by scoring 2 (or more) of 10 Kelp. Sprint 4: Increases above scores for Tilapia and Kelp Scores 410 additional points reliably by scoring 7 (or more) of 10 polyps from opponent's side and 3 (or more) of 10 polyps from our side into reefs and into MPA. Sprint 5: Scores TBD to TBD points reliably by scoring TBD. Sprint 1: Starts, leaves box, stops, moves over bumps on board and through turnstile, all very reliably. Sprint 2: Scores 12 x 10 = 120 points reliably by scoring 12 of 12 Tilapia. Sprint 3: Scores 180 additional points reliably by scoring 6 (or more) of 10 Kelp. Sprint 4: Scores 410 additional points reliably by scoring 7 (or more) of 10 polyps from opponent's side and 3 (or more) from our side into reefs and into MPA. Sprint 5: Scores TBD to TBD points reliably by scoring TBD.

After Sprint 2: Accomplished: Starts, leaves box, stops, moves over bumps on board and through turnstile, all very reliably. Scores 12 x 3 = 36 points reliably by scoring at least 3 of 12 Tilapia. Sprint 3: Scores 12 x 9 = 108 points reliably by scoring at least 9 of 12 Tilapia. Scores 60 additional points reliably by scoring 2 (or more) of 10 Kelp. Sprint 4: Scores 60 additional points reliably by scoring 4 (instead of just 2) or more of 10 Kelp. Scores 30 additional points reliably by scoring 7 (or more) of 10 polyps from opponent's side and 3 (or more) of 10 polyps from our side into reefs and into MPA. Sprint 5: Scores additional points from polyps. Scores TBD to TBD points reliably by scoring TBD. Accomplished: Starts, leaves box, stops, moves over bumps on board and through turnstile, all very reliably. Sprint 2: Scores 12 x 6 = 72 points reliably by scoring at least 6 of 12 Tilapia. Sprint 3: Scores 60 additional points reliably by scoring 2 (or more) of 10 Kelp. Sprint 4: Increases above scores for Tilapia and Kelp. Scores 410 additional points reliably by scoring 7 (or more) of 10 polyps from opponent's side and 3 (or more) of 10 polyps from our side into reefs and into MPA. Sprint 5: Scores TBD to TBD points reliably by scoring TBD.

After Sprint 3: Accomplished: Starts, leaves box, stops, moves over bumps on board and through turnstile, all very reliably. Scores 12 x 11 = 132 points reliably by scoring at least 11 of 12 Tilapia. Scores 30 additional points reliably by scoring 3 (or more) of 10 polyps from our side into MPA. Sprint 4: Scores 30 additional points reliably by scoring 1 (or more) of 10 Kelp. Scores 50 additional points reliably by scoring 8 (instead of just 3) of more of 10 polyps from our side into MPA. Sprint 5: Scores 90 additional points reliably by scoring 4 (instead of just 1) or more of 10 Kelp. Scores … Accomplished: Starts, leaves box, stops, moves over bumps on board and through turnstile, all very reliably. Scores 12 x 3 = 36 points reliably by scoring at least 3 of 12 Tilapia. Sprint 3: Scores 12 x 9 = 108 points reliably by scoring at least 9 of 12 Tilapia.. Scores 60 additional points reliably by scoring 2 (or more) of 10 Kelp. Sprint 4: Scores 60 additional points reliably by scoring 4 (instead of just 2) or more of 10 Kelp. Scores 30 additional points reliably by scoring 7 (or more) of 10 polyps from opponent's side and 3 (or more) of 10 polyps from our side into reefs and into MPA. Sprint 5: Scores additional points from polyps. Scores TBD to TBD points reliably by scoring TBD.

Take-away (summary) Consider Simplified Scrum (an Agile process) Make a Release Plan Repeatedly: Do a Sprint Evaluate Re-Plan KISS – don’t overplan at this point Do detailed planning (i.e., assign Tasks) only for the current Sprint Be agile! What the team has accomplished so far informs what the team can accomplish in the rest of the time! Items in the Release Plan are Deliverables, not Tasks. Most items should score points. Always have working robots that score points Acknowledgement: I am grateful to Sandy Mutchler for her help with the ideas of this project and this presentation of them.