D AGSTUHL S PRINT 2014. D AGSTUHL D ETAILS Internet Facilities Honor System Questions?

Slides:



Advertisements
Similar presentations
Iteration Planning.
Advertisements

What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Agile Planning. The problem with documentation Argument: “Heavy” documentation too much for most business-style projects.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Meeting Management Kellogg School 2 October 2002.
Chapter 11 Requirements Workshops
Managing a Project Using an Agile Approach and the PMBOK® Guide
Planning. SDLC Planning Analysis Design Implementation.
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
AIDA is co-funded by the European Commission within the Framework Programme 7 Capacities Specific Programme, Grant Agreement AIDA status report.
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
What is Scrum Process? Where is it used? How is it better?
DDI Lifecycle: Moving Forward Outcome of the Recent Workshop in Dagstuhl Joachim Wackerow.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
DDI Moving Forward: Sprint 5 Schloss Dagstuhl October , 2014.
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
Project Life Cycle.
Instructional Technologies 7/2013 Week4 More Word Applications & Spreadsheets 1.
MJM22 Digital Practice and Pedagogy Week 9 Collaboration Tools.
A Few Agile Practices Or how to plan who does what over the next two weeks when Iteration I is due C Sc 335 Rick Mercer.
Introducing Project Management Update December 2011.
Sprint 108 Review / Sprint 109 Planning June 3 rd, 2013.
Chapter 5: Process What Is Process?  Process Writing explains how to do something or describes how something is done. There Are Two Types of Process Paragraphs:
Introduction to DDI Moving Forward Dagstuhl Seminar October 22-26, 2012.
Moving Forward IASSIST Sprint. Housekeeping Internet Network: UofT Username: iassist2014 Password: robarts Lunch Toilets.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
DDI Specifications Recent Developments Wendy Thomas Joachim Wackerow Technical Committee EDDI Copenhagen.
SCRUM.
Doc.: IEEE /0054r0 Submission March 2013 Mika Kasslin, NokiaSlide 1 TG1 Closing Report for March 2013 Notice: This document has been prepared.
D AGSTUHL S PR Ï NT O RGANIZING T EAM Sprintmeister: Michelle Edwards Working Group Chairs: Data Description: Steve McEchern Methodology: Michelle.
Welcome To the DDI Model Review and Sprint! Schloss Dagstuhl October 19-23, 2015.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
DDI Moving Forward: Sprint 1 Schloss Dagstuhl October 28-November 1, 2013.
Introducing the INS Master Schedule Wayne Baggett.
SUPPORT THE WARFIGHTER MPE Reference Architecture Development Kick-off Meeting Deputy Director Architecture & Interoperability Office of the DoD CIO Thomas.
NPSTC is a federation of organizations whose mission is to improve public safety communications and interoperability through collaborative leadership.
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Working in Groups in Canvas
Agile Scrum Management
Presenter Name Presentation Date
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Math Field Day Meeting #2 October 28, 2015
Presenter Name Presentation Date
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Chapter 3: The Project Management Process Groups: A Case Study
Presenter Name Presentation Date
Scrum MODULE 3 – Part 3.
Burn Down charts for Project Management
What do you need to know about XP?
Summarizing Our Models to Date
© University of Liverpool
Chapter 11 Requirements Workshops
Presenter Name Presentation Date
Sprint Planning April 2018.
Introduction to Agile Blue Ocean Workshops.
doc.: IEEE <doc#>
Dr. Rob Hasker SE 3800 Note 9 Reviews.
Scrum in Action.
Presenter Name Presentation Date
Presenter Name Presentation Date
(Project) SIGN OFF PROCESS MONTH DAY, YEAR
Sprints.
1st Q, wk #1 Aug , 2018.
Presentation transcript:

D AGSTUHL S PRINT 2014

D AGSTUHL D ETAILS Internet Facilities Honor System Questions?

W HAT ’ S A SPRINT ? Time boxed sessions Specific outputs

T HERE ’ S A REASON … Committed to January 2015 release This week’s goals are crucial for delivery If we are disciplined, we can do it!

S PRINT RULES Accept personal responsibility for Sprint process and outputs Contribute and share generously and openly Actively listen and learn from other’s perspectives and experiences Work collaboratively Participate fully on all tasks

S PRINT T EAM Sprintmaster – facilitator, process, progress, coach Working groups - focus on specific deliverables Support group – resolve issues with deliverables (modelling, classifications, conceptual) Facilitation team – process support (Sprintmaster, organizers, working group chairs)

W HO ’ S W HO - F ACILITATION Sprintmaster: Kelly Chatain Working Group Chairs: Data Citation: Larry Hoyle Simple Instrument: Barry Radler Simple Data Description: Steve McEachern Simple Codebook: Wolfgang Zenk-Moeltgen Organizers: Mary Vardigan, Larry Hoyle, Arofan Gregory, Achim Wackerow, Wendy Thomas

S PRINT P ROCESS Focus on tactical goals Specific deliverables for a set time period (a few hours to a half day) Defined by working groups with help from facilitation team Multiple goals within one session, sub-dividing probable Wash, Rinse, Repeat

M ANAGING THE W ORK Individuals proactively choose their work Estimated work remaining is updated daily (standup/plenary) If work unclear, define a sprint work item with a larger amount of time and break it down later Update work remaining as more becomes known

S TAYING ON T RACK The Parking Lot – for ideas, issues off task or which need more discussion Document it and set it aside Avoid extended debate We do not want to lose track of issues which need to be decided through considered discussion We cannot let them stop us from making progress Visit Parking Lot after each session, update/remove items

S TAYING ON T RACK The Soap Box - you have a brilliant idea (or even just an idea) to present to the group 2 people per day during morning plenary 3-minutes in duration No discussion directly afterwards (future plenary) Added to the parking lot Notify Sprintmaster the day before The answer is 42!

W RITING I T D OWN Update the Wiki *Moving+Forward+Project User: ddieditor Pass: zipscript-3 *Moving+Forward+Project Use the white boards Use the 3x5s and Post-its Take Pictures Drupal

D AILY W ORK S CHEDULE 9:00 - 9:15Morning Standup/Plenary/Soap Box 9:15 -10:30 1 st Working session 10: :45Coffee 10:45 -12:15 2 nd Working Session 12: :45Lunch Facilitation Team meets (13:30 – 13:45) 13:45 – 14:00Afternoon Standup/Plenary 14:00 – 15:153 rd Working Session 15:15 – 15:30Cake & Coffee 15:30 – 16:45 4 th Working Session 16:45 – 17:00 Closing Standup/Plenary Facilitation Team meets (17:00 – 17:30) Schedule may be modified as needed, but this is the standard

S PRINT T OPICS Enhanced Data Citation Simple Instrument/Complex Simple Data Description/Complex Simple Codebook Qualitative/Methodology

D ELIVERABLES Final draft model for review by the Modeling Team All completed objects in Drupal Complete use cases covered by the View with documentation Linked in Drupal A document containing: Description of open issues and discussion Description of decisions made for closed issues Further ideas for future development Parking lot issues list

N OTES ON D ELIVERABLES Data Citation Working Group may have some additional deliverables as a result of NSF funding Not producing a View in DDI, impacting other Views Changes resulting from their work should be made to objects in Drupal Qualitative/Methodology Working Groups are just starting Exploratory in nature May result in Drupal objects – Views are not expected to be completed If planned work is finished before the week is out, there is plenty more to be done!

N EXT S TEPS Draft Views will be submitted to Modeling Team for review Work with content teams to resolve any issues Work to take place virtually before the next sprint Next sprint takes place before EDDI (end of November) Technical and production focus Production teams need finished models to work effectively

I NTRODUCTIONS …….. Hello, my name is… Experience with Moving Forward Areas of interest/expertise