...
Make changes to sak-879 so that we break it apart into pieces that Lisa can relate to fully and to which she can link her testing assets to. If programmers provide Sandra with enough instructions, Sandra will make the changes in Jira. E.g., move 879 to a Topic and then create assets for each of Thomas's work efforts for modules that need to migrate to production. Also link Lisa's testing asset so Lisa can see all of her work queue.
James says SCORM is done for this sprint. James will make Confluence page for the Scorm effort-- functional description, technical notes. Also give the group a demo sometime soon. We need a new story for the remaining work.
Michael will create a new asset for stats fine-tuning for things not yet done. Mike still has unit testing to do. Not sure if we need a new asset for just unit testing. Documentation in Confluence is current.
...
Who is the IOR? We still have this issue. In For the foreseeable future, some sites that need a faculty member included who is not yet identified in Banner will require human intervention.
...
Consider committing sak-800, Automate adding the instructor of Record to a course site that was built for him by a DeptAdmin or other authorized person. This could work in cases in which the IOR is known to Banner and therefore to SmartSite. We don't need this for the 2.4.1 upgrade.
Sak-696, Refactor GradeBook for 2.4.1 upgrade. Jon will create asset assets for this. Clone this story for this next iteration.
...
Who will always complete the VOS copies when we need them? Do we call John Harris for this or do this ourselves? Need to check with John Harris. Thomas is still working with John Harris for the new AFS volumes. The 2.4.1 upgrade is not dependent on this task but we should include this in this sprint. We need this for Fall 2007.
Need to document further the process for the DC's involvement in our upgrades for their tasks. Create a task or story for this. Start with the post doc implementation document from last time as a template. Make sure Prabhu can work Subversion more than just accepting a link. What about when he makes changes to scripts we send him? How do we get his changes into Subversion? He needs to check in the latest changes.
We need to continue focusing on having the DC set up our new application servers, migrate our database to the RAC, and purchase one more client server. The client servers are needed for Fall 2007.
We still need to hire someone for tuning our databases also (not mentioned in the Iteration meeting).