1 / 23

Distributed Team Collaboration Processes II OMSE 556 Final Report (SPRING 2012)

Ivan Dontsov, Andy Phenix, Maureen Rottschaefer. Distributed Team Collaboration Processes II OMSE 556 Final Report (SPRING 2012). Agenda. Status Demo Lessons Learned. Project Proposal.

rob
Download Presentation

Distributed Team Collaboration Processes II OMSE 556 Final Report (SPRING 2012)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Ivan Dontsov, Andy Phenix, Maureen Rottschaefer Distributed Team Collaboration Processes IIOMSE 556 Final Report (SPRING 2012)

  2. Agenda • Status • Demo • Lessons Learned

  3. Project Proposal “The primary objective of this OMSE 2012 Practicum Project is to extend and refine the process specification tool (developed during the 2010 Practicum) and address some of its limitations. In particular, the project will address the ‘most obvious extension’ to provide a more user-friendly interface and easier administrative support.”

  4. Project Process • OMSE 555 (Term 1) • Waterfall • OMSE 556 (Term 2) • Iterative

  5. Roles (planned) • OMSE 556

  6. Roles (actual) • OMSE 556

  7. Project Plan Adjusted • Contingency – Focus only on ‘core’ Functionality

  8. Project Plan Adjusted • Contingency – Focus only on ‘core’ Functionality

  9. Project Plan Revised

  10. Project Status - Development • Planned vs Actual • Iteration 0 – Technical Prototype Complete • Iteration 1 – In Progress Complete • Iteration 2 – In Progress Complete • Testing, Documentation • Behind Schedule

  11. Status of Deliverables

  12. Use Cases Implemented

  13. Project Constraints • Platform • Developer Skillset

  14. Technical Platform • .Net / Mono • Web-based Application • ASP.NetMVC Framework • jQuery • AJAX • Apache / mod_mono • MySQL • MoMA

  15. Project Proposal “The primary objective of this OMSE 2012 Practicum Project is to extend and refine the process specification tool (developed during the 2010 Practicum) and address some of its limitations. In particular, the project will address the ‘most obvious extension’ to provide a more user-friendly interface and easier administrative support.”

  16. Existing OMSE 551 Tool • Set up Assembla user account • Checkout xml templates from Subversion repository • Copy templates and fill out xml content • Commit updates to Subversion repository • Repeat until all content created • Navigate to website • Enter Assembla user account and click ‘Load User’ • Click ‘Build Site’ to process xml content • Click ‘View Built Process Site’ to view process specification

  17. New Tool • Logon to website • Click ‘Create New…’ • Fill in form fields • Click ‘Save’ • Click ‘Preview’ to view process specification

  18. Project Demo

  19. Future Project Work • Notifications • Collaborative Review

  20. Lessons Learned • Project Management Issues • Roles and Responsibilities • Communication Processes • Phased Approach • DSEPS • Limited Use

  21. Project Risks

  22. Q & A

More Related