Play at Work: Applying Agile Methods to Museum Website Development

706 views
623 views

Published on

Dana Mitroff from SFMOMA and Alon Salant from Carbon Five ran this workshop for attendees at the Museum Computer Network annual conference in Austin, October 2010. The focus of the workshop is to give attendees an up front and personal experience with the daily activities of agile software development teams.

Details at http://www.mcn.edu/play-work-applying-agile-methods-museum-website-development.

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
706
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • DANA
  • DANA
    This is a schedule for today .
     
    it's posted up here on the wall in more details so that we can be sure to stay on track, and you can see where we are and where we're going
     
    transparency
    you can help keep us on track
    Review schedule ...
  • DANA:
    -I'm head of Online Services at SFMOMA
    -manage our public-facing website
    -We've been working with C5 for about 7 years
    -most recently on our new website
    -C5 built our new site using their CMS, smilemaker
    - still work together on a daily basis 
    - new features and functionalities 
    -now will let Alon introduce himself
    ALON:- 10 years creating web applications for clients at Carbon Five
    - Always looking for ways to be more efficient and collaborative both internally and in our client relationships
     
     
     
     
  •  DANA:
     
    -now we want to know who you are
     
    -Everyone go around and just say 4 things:
    Name
    Where you work
    What you do
    Why you're here
     
     
     
     
     
  • ALON
    Our goal for today is to inspire you to learn more by providing some insight into the value of non-traditional ways of running projects.
    We're not here to teach you agile but rather to show you some specific practices that may be useful to you and an approach that will help you think differently about how to get work done in your organization.
    How might attendees pursue learning agile and introducing it to their teams after this workshop?
  • DANA
    SFMOMA launched new site in 2008
    Were working with another vendor and at 11th hour they said they could not build our site as spec'd
    Came to C5 and said,  "Can you build this?"
    Answer was "Let's figure out together what we can do and how to get there."
    They had less than 6 months to build and deploy a very complex site
    SFMOMA was totally new to agile process
    We had never worked this way
    But we thought we'd give it a shot
    Was extremely successful for us
    This process took something overwhelming and helped us break it down
  • ALON
    Set of software development practices
     
    Named Agile in 2001 to recognize the difference from 'heavyweight' 'waterfall' practices
    Danger of degrading to "cowboy" coding.
     
    Why Agile?
    Agile is not a panacea, nor are the practices easy. They require regular daily discipline to be effective and an overall organization that is willing to adapt the way it thinks about getting work done.
     
    Wikipedia:
    Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The term was coined in the year 2001 when the Agile Manifesto was formulated.
    Agile methods generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices intended to allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals.
  • ALON
     
    Why Agile?
    History
    Waterfall
    Agile Manifesto
    Developer practices
    Planning practices
     
  • ALON
     
    Written in 2001
    Response to waterfall practices
    Developer v. planning practices
  • ALON
    Standing Daily as an example
    Ritual helps make the daily discipline easy
    Clear rules improve efficiency by defining acceptable behavior
  • ALON set up why we are talking about the calendar:  A slice of a system that we are going to use to illustrate our points. We used this process to build this site and calendar.
    Play along in a fantasy that we are creating the event calendar for a museum building up to what we see here. There may be additional requirements too.
     
    DANA walk through calendar:
    1) Today's event listings-I'll pick November 22) Point out images 
    3) Select a date range (pick Nov. 21-27)
    4) Filtering by category (pick Families)
    5) RSS feed
  • ALON
    People like to group a whole host of activities under the name The Planning Game. 
     
    The key activities are defining requirements, estimating effort and producing a plan for execution.
     
    There are roles for product managers, designers and developers in the Planning Game.
  • ALON
  • ALON
    Good stories are:
     
    Independent
    Negotiable
    Verifiable
    Estimateable
    Sized appropriately
    Testable
     
    http://xp123.com/xplor/xp0308/
  • DANA to read first story
  • ALON
     
    What are roles for?How are they different from Personas?
     
  • Get participants to read the rest of the stories.
  • http://en.wikipedia.org/wiki/INVEST_%28mnemonic%29
     
    Small or Sized Appropriately
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • ALON
    Good stories are:
    Independent
    Negotiable
    Verifiable
    Estimateable
    Sized appropriately
    Testable
  • ALON
    Alon intro 
    Point-based v. time-based estimation 
    Velocity 
    Also mention Planning Poker
    Volunteers estimate prewritten + solicited stories
    Estimates go on giant post-its
  • ALON
     
    How do you capture requirements today?
    Do you do estimates? How? Do they work?
    Can you imagine doing this with your teams?
    Could this work in your organization?
     
  • ALON
  • Alon describes story mapping
     
    SHOULD WE HAVE THEM BREAK INTO TEAMS NOW? Or wait until after we read stories?
    Alon pick image from http://www.agileproductdesign.com/blog/the_new_backlog.html?
  • ALON
    Set up why we are talking about the online collection and the visit section.
    - We are going to use stories from these parts of the SFMOMA site with story mapping.
     - Just as we did with the calendar, play along in a fantasy that we are creating the online collection and the visit section of the site. There may be additional requirements too.
     DANA--COLLECTION STORIES:
     
    1) Browse by last name
    2) Search the collection so I can find info on artists and artworks
    Do search for Robert Bechtle
     
    3) Discover related contentGo to Gran Torino
    Point out related content
     
    4) Note artwork status -- Gran Torino not on view
     
    5) Watch embedded video of Bechtle from Gran Torino screen
     
    6) Check other works by Bechtle -- see SFMOMA has a few, but only 1 on view right now
  • DANA walk through Visit
     
    VISIT STORIES:
     
    1) Main Visit page content with hours + directions
    2) Interactive map on Visit page--embedded Google map
    3) Tickets page with pricing info, link to buy online
     
    4) Food + Drink section-- click through to sample menu
    5) Kids + Families page --see events pulled from calendar into here
    6) Main visit page -- click to foreign language PDFs
     
  • ALON? or DANA?
    Now we're going to review the stories that go with these two areas of the site.
     
    You have these in your card sets ...
     
    DANA read first story
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Get participants to read the rest of the stories.
  • Hand out white index cards w/ all stories to 2-4 teams, also colored cards & sharpies
    Map for 15 min
    Teams describe their plans
    Alon pick image from http://www.agileproductdesign.com/blog/the_new_backlog.html?
  • Alon intro, regular schedule
    B's & C's (benefits and concerns)
    Group 3 min on stickies
    Everyone shares their stickies, posting in clusters
    Review Bs
    Review Cs, identifying action
     
    Identify smart goals
    S - Specific
    M - Measurable
    A - Achievable
    R - Relevant
    T - Time-boxed
    http://en.wikipedia.org/wiki/SMART_criteria
  • Group 3 min on stickies
    Everyone shares their stickies, posting in clusters
    Review Bs
    Review Cs, identifying action
  • ALON TO DO: 
    repost on blog
  • ALON
  • BOTH
  • Play at Work: Applying Agile Methods to Museum Website Development

    1. 1. Play at Work: Applying Agile Methods to Museum Website Development October 27, 2010 Museum Computer Network Conference Dana Mitroff Silvers Alon Salant SFMOMA Carbon Five
    2. 2. Today's Plan Introductions Us and You! Project Background What is Agile? Let's play some games! Story Writing Ro! Cham! Beau! Break @ 3 p.m. (15 min) More games! Story Mapping Reflection Discussion + Questions
    3. 3. Introductions: Us
    4. 4. Introductions: You 1. Name 2. Where you work 3. What you do 4. Why you're here
    5. 5. Why We're Here http://www.sfmoma.org/artwork/18434
    6. 6. Project Background
    7. 7. What is Agile?
    8. 8. Some Key Attributes Iterative Adaptive Collaborative Transparent
    9. 9. Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
    10. 10. Games in Agile Ritualized activities Cooperative, not competitive Simple, repeatable rules Participants create the experience
    11. 11. SFMOMA Calendar
    12. 12. The Planning Game
    13. 13. Let's Play Some Games! Requirements with Story Writing Estimation with Ro! Cham! Beau!
    14. 14. Story Writing (Requirements) As a <role>, I can <what> so that <why>.
    15. 15. Sample Story #1 As a Local Visitor I can see a list of today's events so I can decide if I want to go to the museum.
    16. 16. A Word About Roles Local Visitor Online Visitor Tourist Educator Parent
    17. 17. Sample Story #2 As a Tourist I can choose a date range for events so I can decide if I want to visit the museum when I'm in town.
    18. 18. INVEST in Stories Independent Negotiable Verifiable Estimateable Sized appropriately Testable
    19. 19. Sample Story #3 As a Parent I can filter events by category so I can just see the "Family Programs."
    20. 20. Sample Story #4 As a Local Visitor I can subscribe to an RSS Feed so I can stay up-to-date with events at the museum.
    21. 21. Sample Story #5 As a Local Visitor I can see thumbnails with exhibition listings so that I can get a sense of the art.
    22. 22. Story Writing on Cards (3 min) As a <role>, I can <what> so that <why>.
    23. 23. Share Your Stories
    24. 24. Ro! Cham! Beau! (Estimation)
    25. 25. Discussion   How do you capture requirements today? How do you estimate work?  Can you imagine doing this with your teams?  
    26. 26. Break (return at 3:15) http://www.sfmoma.org/artwork/48140
    27. 27. Let's Play Some More Games! Prioritization with Story Mapping  Reflection 
    28. 28. Story Mapping (Prioritization) 
    29. 29. Online Collection 
    30. 30. Visit 
    31. 31. Collection Story #1 As an Online Visitor,  I can browse artists by last name so I don't have to worry about spelling.
    32. 32. Collection Story #2 As an Online Visitor, I can search the collection so I can find info on artists and artworks  at SFMOMA. 
    33. 33. Collection Story #3 As a Online Visitor I can see content related to an artwork (e.g. exhibitions, events, and multimedia) so I don't have to hunt around for it. 
    34. 34. Collection Story #4 As a Local Visitor I can see if a work is on view so I can decide if I want to visit the  museum. 
    35. 35. Collection Story #5 As an Educator I can watch a video of an artist talking  about his/her work so I can learn more about the artist. 
    36. 36. Collection Story #6 As a Tourist I can see other works SFMOMA has by  an artist so I can decide if I want to visit.
    37. 37. Visit Story #1 As a Tourist I can get hours and directions so I can plan my visit.
    38. 38. Visit Story #2 As a Local Visitor I can use an interactive map so I can figure out the best way to get to the museum.
    39. 39. Visit Story #3 As a Local Visitor I can check ticket prices and buy tickets online so I can save time.
    40. 40. Visit Story #4 As a Tourist I can find out what kind of dining the museum offers and see menus so I can plan my visit.
    41. 41. Visit Story #5 As a Parent, I can see upcoming family events from the calendar so I can plan when to visit.
    42. 42. Visit Story #6 As a Tourist, I can access basic visitor info in my language so that I can plan my visit.
    43. 43. Story Mapping in Teams (15 min)
    44. 44. Reflection Regularly, not just at project end Per milestone (every 2-4 weeks) B's & C's (Benefits & Concerns) Identify a couple SMART goals
    45. 45. Three-Minute Reflection http://www.sfmoma.org/artwork/111624
    46. 46. Resources + Tools http://bit.ly/mcn-play
    47. 47. Just a Taste Great for bringing your team together Focus on efficiency Many more practices out there
    48. 48. Discussion + Questions Alon alon@carbonfive.com @asalant Dana dmitroff@sfmoma.org @dmitroff

    ×