April 2011 - Tiger Team experiences and how to get involved

We will hear from Tiger Team members about what they do in the four phases of development of each NIS subsystem: Inception, Elaboration, Construction, and Transition. Mark Servilla will explain our role in building a NIS that works for us.

The descriptions of the NIS subsystems:

Tiger Team resources include:

  • What is a Tiger Team?
  • Join a Tiger Team?
  • Membership Roster
  • Acceptance Testing
  • The NIS subsystems are described on the Architecture (forums)

    The schedule of the development phases for each subsystem shows when Tiger Teams can expect to be on call.

    Google Doc showing cross-reference of LTER Sites with Tiger Teams: google doc spreadsheet

    PASTA Component Name Changes (https://docs.google.com/drawings/edit?id=1YK6i3efcVNQGOe4pNmY3Iz4srSxo8S...)

    Monday Notes

    See attachment below.

    Tuesday Notes

    Participants: Corinna Gries, Mark Servilla (co-leaders), Dan Bahauddin, Karen Baker, Sven Bohm, Emery Boose, James Brunt, Gastil-Buhl, John Chamblee, Duane Costa, Jason Downing, Stevan Earl, Nicole Kaplan, Margaret O’Brien, Aaron Stephenson, Bob Waide, Yang Xia

    See power point on IM website for more details.

    Tiger teams are a resource for NIS programmers. It is important for members to be able to respond on short notice. Three members per team has proved to be a good number. Members are asked to test new features and provide formal feedback. Looking for more participation.

    Tiger teams are also a mechanism for providing feedback out to the community (bidirectional approach). In addition, they provide an opportunity for members to learn fundamental aspects of the services under development. A great learning experience for particular technologies (e.g. Internet security mechanisms).

    Bob Waide: Community feedback on the NIS is essential. Tiger teams are one way to make sure this will happen. Everyone is busy but please carve out some time. I’m willing to speak to your site PI.

    Need to get domain scientists and graduate students to participate. Small bribes are available for the latter. The more help at this stage the better the result will be.

    Stevan Earl: As a domain scientist it was exciting to be on a tiger team but as a non-technical participant I was not able to contribute as much as I wanted to.

    Mark spends a lot of time organizing and coordinating the tiger teams. LNO is considering hiring a part-time person. Gastil has offered to help organize the tiger teams and update the website. Other IMs might contribute in this way.

    Consider how to facilitate participation by domain scientists. E.g. scientists could provide feedback on analytic functionality.

    Slide 3 shows the evolution of names for system components.

    See IM or NIS websites for a list of current tiger teams and how to volunteer.

    The NIS development team welcomes participation at any level, including code review. But in general the need for help is greatest at the beginning and end of the development cycle.

    The metadata management tiger team is done. The event manager and metadata factory tiger teams are nearly done. Metadata management is active. Identity services is starting up.

    Identity services includes authentication, authorization mechanisms (not just data but also services), resource protection, and computer security.

    How to update the LTER data access policy for Pasta? Need to create a working group to address this issue.

    Time commitment for tiger teams depends on the life cycle. Average is less than 1 hour per week, with a maximum of 2-3 hours per week. Members can volunteer to do more (e.g. review code). Not a lot of time but important to respond quickly. Usually 1-2 week notice for a meeting. Everyone recognizes that members are volunteers.

    Mark is three-quarters NIS and one-quarter DataONE. There is some synergy in these activities (e.g. authentication). Mark normally devotes one day per week to DataONE.

    The NIS should not be developed in a vacuum. Developer participation with DataONE, NEON, etc is helpful up to a point. Bob is watchful of the time commitments for LNO staff.

    The same holds true for individual sites. Site IMs volunteer to work on network and community projects in part because of the benefits to their own sites.

    The NIS developers regard the tiger teams as critical to the success of the NIS. E.g. tiger teams provided lists of candidate EML files and quality control checks for the data manager suite. Tiger team input is used and has led to design changes.

PASTADataflowNameEvolution.png73.83 KB
Monday Notes (WaterCooler_4Apr2011_TigerTeamExperience.doc)325.5 KB
PPT outline for Tiger Team discussion (tiger_team_experiences.ppt)955 KB


Network News article

There was an article written by Duane in the LTER Network News in December 2010 about Tiger Teams: http://news.lternet.edu/Article2268.html