Project Brief EECS 690: Agile Software Development Team Name.

Slides:



Advertisements
Similar presentations
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Advertisements

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.
Principles of Agile management of software development project 28 November 2014.
Scrum Research at Carnegie Mellon Mark C. Paulk, Ph.D. March 16, 2009 Scrum Gathering, Orlando.
IAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming.
(modified for the use of AgilEFant project and LC2.0. group by Touko Vainio-Kaila from the original slides of Jarno Vähäniitty) Helsinki University of.
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.
The Business Analyst Role in Agile Projects
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.
Miser-C MISRA-C Compliance Checker Ian Biller, Phillippe Dass, Bryan Eldridge, Jon Senchyna, Tracy Thomas.
The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team.
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
Cyreath.co.uk Empirical Pragmatic Testing Copyright ©Mark Crowther 2009 An introduction to SCRUM Agile Project Management Mark Crowther – Empirical Pragmatic.
1 Agile Methodology & Programming Ric Holt July 2009.
10/8/2008Clarity PLC Fall WebConference This slide copyright Jeffrey A. Bloom Tips and Techniques Leveraging Clarity’s Notes Facility & SCRUM in.
Software Development and Release Management By James Lawrence Software Development Manager.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Project Workflow. How do you do it? -Discussion-
SCRUM Not your average bacon and eggs. The Basics Product Backlog Sprint Backlogs Sprints – The Daily Scrum – Burn-down chart Sprint Retrospective.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
Enterprise Project Management
Scrum Practices Sprint-2. Agenda Scrum Master Product Backlog Scrum Teams Daily Scrum Meeting Sprint Planning Meeting Sprint Sprint Review.
Richard Product Owner Development Team Scrum Master Increment Sprint Backlog Lorem ipsum dolor sit amet, consectetur adipiscing elit.
OV-1.1 CSE4939 CSE4940 Reviewing Concepts  The Agile Methodology   scrumreferencecard.com/ScrumReferenceCard.pdf.
SCRUMBAN?!?! What is it and how can it help your team?
Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
The Scrum Framework with Team System Andy Leonard VSTeamSystemCentral.com.
Senior Projects Meeting 7 September 9, Agile Development Process The players are Product owner: sets priorities, owns in the sense of is responsible.
Computing Facilities CERN IT Department CH-1211 Geneva 23 Switzerland t CF SCRUM Do’s and Don’ts ITTF 31 May 2013 Miguel Santos CERN IT/CF.
Giving order to the chaos of agile Presented by Matt Campo CSC 490 Fall 2015.
IDeaWorks- Good To Great – Program Hisham Al Zanoon July 5, 2012.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
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.
The Agile Manifesto Some thought starters for Ogilvy on how to work with Agile and SCRUM approaches to managing projects.
CSE Senior Design II Day 1: Getting Organized Spring 2016 Instructor: Mike O’Dell.
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Created By:-
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
What’s New in SPEED APPS 2.3 ? Business Excellence Application Services.
Using Scrum to Improve Teamwork, Communication, Quality and Speed.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Working Agile in Software Development July-2016 Oracle Confidential – Restricted.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(3)
Copyright © Curt Hill Scrum Software Development Paradigms What is a Scrum?
Business Intelligence in Classroom WHY:.  Purpose – knowledge to make an informed career decision  Process – Use Scrum method of project management.
Utilize Agile Project Management for GIS Projects Jennifer Prather and Lana Tylka.
Flight Software Conference 2016
The Strategic Role of Information Development in Continuous Delivery
Scrum.
Agile Training Day 2 November 17, 2015.
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
Not your average bacon and eggs
COMP 135: Human-Computer Interface Design
Agile Software Development Brian Moseley.
By: By: Agile Scrum Master Online Training.
Scaled Agile Requirements: What, When & How
Product Backlog List of things that needs to be done to make the product come into existence 
Impact of Agile Methodology on Software Architecture
Chapter 3: The Project Management Process Groups: A Case Study
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
Project Management and the Agile Manifesto
Agile Project Management
Johanna Rothman Agile Team Measurements Chapter 12
SUCCESS MANTRAS FOR BEING AN EFFECTIVE INFORMATION DEVELOPER IN AGILE
SCRUM from product owner point of view
Scrum Overview.
Sprint Review.
Presentation transcript:

Project Brief EECS 690: Agile Software Development Team Name

Agenda Product Demonstration Product End State Product LOEs Sprint Progress Check Target Status on LOEs Lessons Learned Methodology Sustains & Improves Miscellaneous / Other Issues Questions Update Agenda to reflect your brief

Product End State Briefly show/talk about: –Final product end state –How the product end state evolved –How the product end state affected the development of the product backlog –How well did your final increment meet the end state conditions

Product LOEs Briefly show/talk about: –Final updated LOEs –How the LOEs evolved –How the LOEs affect the development of the product backlog, sprint backlog, and overall architecture

Sprint Progress Check Briefly talk about: –Usefulness of Sprint Progress Check (Sprints 3 & 4) –What changes need to be made to make it better –Recommendation to either keep or get rid of Sprint Progress Check

Target Status on LOEs Briefly talk about: –Usefulness of Target Status on LOEs (Sprint 4) –What changes need to be made to make it better –Recommendation to either keep or get rid of Target Status on LOEs

Lessons Learned Lesson learned during Sprint Retrospective Another lesson learned during Sprint Retrospective

Targeted Scrum Sustains First area/feature that worked well based on methodology used Second area/feature that worked well based on methodology used Additional area(s)/feature(s) that worked well (if applicable)

Targeted Scrum Improves First area/feature that needs improvement based on methodology used Second area/feature that needs improvement based on methodology used Additional area(s)/feature(s) that needs improvement (if applicable)

Miscellaneous / Other Issues Chance to capture to other issues or topics that do not match the other slides, but need to be addressed Optional slide – use if necessary

Questions?