• Created by user-29b81, last updated on Oct 23, 2008 1 minute read

Members - Sue, Benoit, Christine, Casper, Jean, Ned - problem assigned (problem ID 4)

  • No labels

1 Comment

  1. user-60629

    Nov 07, 2008

    Comments and questions from Stephanie and Butch...


    • Great job working as a team to come up with a usable pilot.  This tracker looks to be immediately usable as a repository and shows great promise for evolving into a standard LL tool.
    • Have you fully tested whether view of the SF trackers are fully public? 
    • We see you have made some modifications to the SForge Project.  The Project Home Page looks like a good place to include info on how to use the tracker (e.g. , that it is public and that private LL's should be addressed elsewhere, what does each field mean, how do you use the data other than as an action item, how do you "email" an item to the tracker, etc).
    • Do you want to include a link back to the LLWG?
    • How do we arrange update access for all PM stakeholders across CU?
    • Who might be the "administrator" of this (monitor it to be sure it is not being spammed, misused, etc)?
    • The "search tracker" seems very capable, but after viewing it, noticed the "Assigned To:" and "Submitted By:" fields...  Lessons Learned will need to be submitted by anyone in a PM role.  They can be assigned to anyone at (or working for) CU.  Thoughts?
    • Is it possible to add another custom field, Project Name?   And can that custom field be used as a part of the Filter SourceForge provides?
    • Is the "Description" the same thing as the "Issue"?  If not, where would the "issue" (i.e. actual example that spurred the lesson learned) be captured? 
    • We suggest working with the Best Practices team to ensure that all data elements needed by the BP process are captured within the repository, such as:

          * If the "Group" for the LL artifact is "Project Management", would it be useful to specify "Phase" to distinguish LL's from the analysis from LL's from development, etc? 
          * Anything else, such as "Project Type" that separates Small Projects from Capital Projects from No Project?
          * Perhaps ask the Best Practices team if they can come up with a "Best Practices" way to use the repository?

    • How might this be used for metrics/measurements?  SForge can be used to generate Reports from the Trackers (add instructions on how to do that), but how can we count and tell which are "repeat items"?