Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Supporting Daily Scrum Meetings with Change Structure

2,393 views

Published on

Jessica Rubart and Frank Freykamp propose a flexible cooperative task board for supporting daily scrum meetings. Change structure is introduced as a means to explicitly model changes in task management.

Published in: Technology, Spiritual
  • Be the first to comment

Supporting Daily Scrum Meetings with Change Structure

  1. 1. Supporting Daily Scrum Meetings with Change Structure Jessica Rubart and Frank Freykamp
  2. 2. Contents Scrum • Scrum • Daily Scrum Meetings Requirements • Requirements Approach • Approach • Combining Hypermedia Domains Prototype • Flexible Cooperation Support Related Work • Explicitly Model Change & Special Views • Prototype Implementation Conclusions • Related Work • Conclusions and Future Work Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  3. 3. Scrum Scrum Roles Requirements Scrum Master Product Owner Team Approach Communication Prototype Sprints Related Work Continuous improvement Conclusions Artifacts Vision Increment of functionality Product Backlog Sprint Backlog Selected Product Backlog Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  4. 4. Daily Scrum Meetings Scrum • Sprint Backlog: Requirements • Backlog Items Approach • Tasks Prototype Related Work • Impediment Backlog Conclusions • Sprint Burn Down Chart » Support for distributed teams & improve retrospectives Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  5. 5. Particular Requirements Scrum (1) Ease of use; similar to a physical whiteboard Requirements (2) Easy access to a virtual task board, e.g. through a Web 2.0 interface Approach (3) Cooperative access to and manipulation of the Prototype task board (4) Support for managing and evaluating the life cycle Related Work of tasks Conclusions (5) Creation of charts or reports based on a given sprint backlog Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  6. 6. Approach: Combining Hypermedia Domains Scrum • Natural Scene Paradigm Requirements • Spatial • Navigational Approach • Taxonomic Prototype • Visual Related Work tagging Conclusions • Split column for splitting tasks Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  7. 7. Approach: Flexible Cooperation Support Scrum • We model a task board like a shared workspace Requirements • We model backlog items, tasks, user representations, etc. like shared objects Approach Prototype • Concurrency control Related Work • Change propagation Task Board Individual views coupled through Conclusions shared objects Persistent shared Supporting Daily Scrum Meetings with Change Structure, objects Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  8. 8. Approach: Explicitly Model Change Scrum Metamodel Taskmodel «ChangeLink» Requirements «metaclass» split n Classifier «Node» «ChangeLink» Approach Task SpatialStructure 1 1 1 text: String pos: Position «Stereotype» «Stereotype» person: String column: State Prototype Link Node estimation: Integer row: BacklogItem n 1 Related Work «ChangeLink» «Stereotype» m 1 ChangeLink «Node» «Node» Conclusions Impediment BacklogItem user: String timestamp: Date text: String text: String Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  9. 9. Approach: Special Views Scrum • Based on a current sprint backlog special views can be generated Requirements Approach Prototype Related Work Conclusions Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  10. 10. Prototype Implementation Scrum • Web Web Browser Web Browser Framework AJAX-based AJAX-based Requirements Task board GUI Task board GUI Echo Approach • Java «HTTP» «HTTP» Prototype • JavaScript Servlet Container • AJAX Echo-based Task board servlet Related Work • JFreeChart View Controller View Controller Conclusions • O/R-mapper Database Shared Model Model «JDBC» using JDBC Persistent Model Shared Model Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  11. 11. Related Work Scrum  Hypermedia Domains Requirements Change Structure can be seen as a separate domain or as an addition to existing domains. Approach  Spatial hypertext applications Prototype  Tools for agile software development  Existing tools for supporting daily scrum meetings Related Work  Version Control Conclusions Our focus: Explicit modeling of changes Flexible cooperation support based on shared objects Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  12. 12. Conclusions and Future Work Scrum • Main contributions for the hypermedia community: Requirements • Applying and combining different hypermedia domains to supporting daily scrum meetings Approach • Introducing change structure as a means to explicitly model change in a flexible way Prototype Related Work • Future Work • Make available the cooperative task board as a Conclusions Web 2.0 platform for evaluation • Apply concept of change structure to other application domains Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009
  13. 13. Thanks for your attention! Scrum Contact: Jessica Rubart (info@jessicarubart.de) Requirements Frank Freykamp (frank@freykamp.com) Approach Prototype Related Work Conclusions Supporting Daily Scrum Meetings with Change Structure, Jessica Rubart and Frank Freykamp, Hypertext'09, 30.06.2009

×