OLE Development Managers Meetings

October 3, 2012

  1. Describe
    1. Use Case Development (2 developers full-time)
    2. Estimates
    3. 2 devs need to stay on instance editor for final bug fixing until next week. 
    4. Vijay will give an email of how a deliver dev can move to KFS 5.0 testing and bug fixing and Poonima 
    5. subtasks for 2557 and 2769
    6. performance is down to 3.5 hours on 1 million records
  2. Deliver
    1. Design Specifications
    2. Module design and process specifications (2 on module overview) 
    3. Patron out by next week - checkout will be out next week or two weeks - Developing the gaps now and will be able to promote code. 
    4. Vijay will give me hours for checkout and patron - gaps  - Patty needs to update timeline.
  3. S&A
    1. Functional Spec Patty get specs lined up. Team working on bug fixes. Prem
    2. License Request will move this week with the exception of the Rice dependencies Patty follow up with Rice Team of their timeline.
  4. System Integration
    1. 5.0 Testing Environment - is up and running - scripts can be run on this environment -
    2. CM Pool Test environment is up and running - we need to deploy to it and test it out - then cutover this Friday
    3. CM Dev environment is live for developers
    4. Discovery Layer integration - 3275 - 
    5. Instance Editor schema changes  - handed off to Tirumalesh team - established just bug fixing until kDays
    6. Kuali Days - presentations - showcasing - may need dev team to help out/editor - KRAD and developing editors
    7. Jeff - Performance environment - we should formalize this environment - his job was to get us to auto builds - 
    8. 3256 - licensing audit failures
    9. Moved a bunch of jiras to SI - check in with Peri.
  5. Review Timeline
  6. CLA for all shadow development staff

September 25, 2012 - KFS 5.0 Upgrade

  1. 5.0.1 - sub-task should be closed for 5.0 and a new one opened
  2. Testing - null exception fixed - hope to have testing completed by Friday this week if no major issues occur. Need Rich to assist with testing of insufficient checking.
  3. Environment setup - Peri still having challenges with OLEFS install. Working with Jonathan and Suresh to put this together. Peri will have an update tomorrow. He should have everything stable by Friday.

September 20, 2012

  1. Top Priorities for Next Week

    1. Dev Environment Stabilized - CRITICAL - PERI Lead
      ###Dev - environment needs to be stabilized - then we can begin promoting daily.
    2. KFS 5.0 Upgrade - CRITICAL - JONATHAN & PERI Lead
      1. Null exception reviewed and fixed (JK/Suresh)
      2. Test Environment Established - (Peri/Suresh)
      3. Upgrade with FINAL 5.0 baseline code - (Jonathan)
  2. Rice/Cancel button we need to to stay with Rice standard - Action Item: Patty follow up with Rich.
  3. Deliver
    1. Reconciling data requirements and configuration requirements with specification.
    2. Almost done with WBS. By this Friday we should have first draft of WBS.
    3. Vijay will assign sub-task to those who are producing the Design.
  4. Address resource issue, i.e., manage bug/fixes while major development is continuing. If CRITICAL/BLOCKER developer that promoted code will fix, otherwise will be scheduled for fixing. Action Item: Patty follow up with Rich on this process.
    #Next SPRINT:
    1. License Request
    2. Need to plan for items to be included for Kuali Days *Action Item: Patty schedule with Peri/Rich Tuesday discuss what is ready for next sprint
  5. Specifications
    1. Action Item: Patty review specifications with Peri and Manoj and create development space for design effort.

September 13, 2012

  1. Deliver - Vijay
    1. Checkout - Jira 2757 / OLE 2921 is this the jira that has functionality that was missed?  If so, we need to add a sub-task for this functionality to be designed and addressed unless it already has been.  I have a note from 8/13/2012 that Peri was going to look at it and it needed to be re-assigned from Vivek. 
    2. WBS - Ready by when? 
  2. Describe - Tiramulesh
    1. Refactor of Docstore - OLE 3132 - we budgeted for 1500 hours - we are at 1233 - Action: Patty send J Pillans write up/need additional 160 hours for instance sub-task
    2. Instance Editor - OLE 2555 - has 1149 hours and work still to be done. Action: 2557 s/b sub-task of 2555. Peri reconcile 2555 today.  Need to review the details and figure out exactly what is going on here.  Jira is confusing, some issues linked  are tasks that require work to complete the editor, other are just related links. Need to know what is really outstanding here.
    3. OLE 2557 - Create and Edit Instance Item - Functionality, adding a sub-task that is "create and edit instance & item Roles and Permissions"
    4. OLE 1995 - Is this even relevant anymore? Search: Docstore Bib Search with Checkout & Checkin - Peri mentioned this may not even be needed anymore. Action:  follow up with Kathy?
    5. There are other FSpecs ready, with CSpecs in progress.  We should discuss if it makes sense to begin use cases on these. Action:  Tirumalesh will begin review... we will check in Tuesday.
    6. Overview document from Lead SME almost ready.
  3. System Integration - Peri
    1. OLE 3016 - KFS 5.0 Upgrade - reduced the estimated hours from 2400 hours to 600.  Based on JK's estimates there are only about 270 hours remaining on the work.  Some of the work relies on all developers testing the environment and checking code.   Have not seen much activity since last week.  Wondering about Suresh's progress on testing.  I am sharing with the FC that we have at least 3 to 4 more weeks on the remaining steps for the upgrade. 
    2. CM Cut-Over for Devel - status?
    3. Circulation Standards - OLE-2849 - we are 248 hours over.  Need to know estimate of hours to completion. 
    4. Refactor OLE Rice 1 and 2 - OLE 3131 - we have logged 1,691 hours on this so far.  What is involved here, how  many more hours can we expect?
  4. Select & Acquire - Manoj
    1. License Request - at 870 hours, do we have any idea how many more hours? ACTION: Manoj - will provide additional hours
    2. I have yet to reconcile Select & Acquire
  5. CRITICAL ISSUE - We must identify the functionality that must be in place for Chicago and Lehigh to install the application and begin importing their data. ACTION ITEM;  Develop steps to convert data and migrate for implementers. Spell this out for FC that this is our approach, determine from FC if there is any user functionality that implementers also need earlier than later.
  6. What will we have ready by Kuali Days? Action Item:  Coordinate with  Peri/Rich (.6 Bib Editor and KRMS ingest never been shown - License Request, Instance Editor)

Open Action Items

  1. Design example shared with Manoj/Peri/Patty (Vijay)
  2. Design template drafted (Manoj)
  3. Reconcile Jiras to Project Plan - (Patty)
    1. Deliver - 80% Complete
    2. Describe - 10% Complete
    3. Select & Acquire - 0 % Complete
    4. System Integration - 10% Complete

August, 23, 2012

  1. Deliver hand-off
    1. identify 8 developers for team (Vijay) DONE
    2. review deliver overview/specifications for planning meeting (Vijay) DONE
    3. PM/DM planning meeting scheduled for Tuesday, 8/28/2012 DONE
    4. update Jiras with component-deliver (Patty) DONE
    5. reconcile spec stories to jira and PM Report OPEN - 80% Complete
  2. identify number of developers required for other teams as a starting point (Patty) DONE
  3. prepare describe for hand-off (Patty) OPEN-IN PROGRESS
  4. Report on performance
    1. Report will be added to jira (Tirumalesh)
    2. Coordinate follow up with John P/Peri (Patty)
    3. Report on docstore and how it relates to refactor work (Patty)
      1. John Pillans will have report completed and distributed to Dennis,JimT by 08/24/2012
  5. Future PM meetings (Patty)

Development Managers Expectations

Area

Expectation

 

Jira

Comments will be used for progress, escalation of issues, clarification of functional, technical and anything relevant to the delivery of the Jira.  EMAIL is not our source of communication for Jira activity.  Feel free to request SME's, Lead SME's, etc.. to place questions, concerns, etc... in jira and not use email when it makes sense. Jira allows a variety of people to keep abreast of activities vs. a subset of people.
Work shall be logged on jiras in order for us to track the effort expended on an issue. 
All activities should be associated with a STORY that is tracked on the Project Managers project plan.  The PM is notified when an issue is created.  These will be monitored to ensure we have items related appropriately.

 

Availability

Notify Project Manager and Lead SME if you are out ill, or vacation, etc...

 

Operated as a Community Resource by the Open Library Foundation