Deletions are marked like this. | Additions are marked like this. |
Line 7: | Line 7: |
= Priorities = | = High-Priority Goals = |
Line 9: | Line 9: |
1. Complete final V2 MVA features & configuration 1. Get V2 into the hands of reviewers 1. Deliver to first paying customer |
1. '''Complete final V2 MVA features & configuration''' 1. '''Get V2 into the hands of reviewers''' 1. '''Deliver to first paying customer''' = Planning = 1. AH/JK - agree JK tasks/priorities & write up in [[V2Planning#JK_Work_Schedule|JK Work Schedule|]] wiki page - ''highest priority'' 1. JK - update V2UsabilityReview wiki page - ''high priority'' 1. Review & update V2LaunchPlan - ''lower priority'' = Upcoming Working Sessions: 04 to 15 November 2013 = 1. Define releases - '''AH/JK''' by phone based on notes to be supplied by JK (AH/JK 2013-11-05, Tue at 11:30). Proposed releases * '''R1''' - Organizing and sharing * '''R2''' - Structure Collaboration * '''R3''' - Project Management * '''R4''' - Scheduling 1. Usability review - '''AH/JK''' working separately: * '''AH''' to supply list of recently updated items * '''AH''' to update JK v2p0 system ([[http://v2.softxs.ch/v2p0-jk]]) with latest software * '''JK''' to review V2UsabilityReview wiki page & own notes and compare with current software * '''JK''' to supply complete replacement for V2UsabilityReview wiki page (keeping '''TN''' notes) * '''AH/JK''' to diScuss any complex or unsatisfactory items & set priorities 1. Develop demo scenarios & write end-user documentation * Scoping statement, for each proposed demo system * Make list of demo systems to produce (smaller demos, drawing manager, meeting manager, site investigations) * Make list of important transactions to demonstrate * Prioritize list & do the first ''n'' items * Update (minimum required) demo configuration and configure demo accordingly * Create demo data * write up user instructions/documentation 1. User roles & project structure design - Schedule '''AH/JK''' working session (mid/late this week?) |
Line 15: | Line 44: |
1. Setup 8-core Intel rackmount server to replace existing zg-3 server | 1. Setup 8-core Intel rack-mount server to replace existing zg-3 server |
Line 17: | Line 46: |
1. Install 'Ubuntu 12.04.3 LTS Server' | 1. Install ''Ubuntu 12.04.3 LTS Server'' |
Line 19: | Line 48: |
1. Install Virtual``Box & Vagrant | 1. Install ''Virtual``Box'' & ''Vagrant'' |
Line 21: | Line 50: |
1. rinetd port forwarder | 1. ''rinetd'' port forwarder |
Line 25: | Line 54: |
1. Setup VM suitable for hosting DrawMGT | 1. Setup VM suitable for hosting Draw``MGT |
Line 40: | Line 69: |
1. Look into Google (or other) web analytics '''JK''' | |
Line 42: | Line 72: |
1. Look into backups at Amazon & Google 1. Look into ''style guide'' for web site |
|
Line 56: | Line 89: |
1. Prioritized list of next V2 features to implement. Proposed releases 1. R1 - Organizing and sharing 1. R2 - Structure Collaboration 1. R3 - Project Management 1. R4 - Scheduling |
1. ''Workflow & User Role'' working paper in preparation for working session 1. Prioritized list of next V2 features to implement. |
Line 62: | Line 92: |
1. Decision/design of multi-file uploads (will be difficult to implement) | 1. Final review of multi-file uploads |
Line 87: | Line 117: |
1. File handling | |
Line 88: | Line 119: |
1. Requirements for Pöyry Uma Oya system (first V2 customer) | |
Line 90: | Line 122: |
1. Review pricing vs. Hydro-2013 survey results | |
Line 94: | Line 125: |
1. Make spelling and grammar fixes 1. Install new features text 1. Install specification draft |
1. Review for spelling & grammar errors & make corrections 1. '''AH''' - Install new ''Features'' web page text - '''high priority'' |
Line 98: | Line 128: |
1. Complete outline | 1. Complete PM outline |
Line 100: | Line 130: |
1. Write some 'news articles' 1. Outline for a webcast |
1. Start writing chapters 1. Configuration handbook - ''part of PM Handbook? Priority?'' 1. Configuration checklist 1. Quickstart Guide - ''part of PM Handbook? Priority?'' 1. Install specification draft - ''lower priority'' 1. Write some ''news articles'' - ''lower priority'' 1. Outline for a webcast - ''lower priority'' |
Line 105: | Line 140: |
1. Final updates to Hydro demo - '''JK''' 1. Final tuning of WBS 1. Complete ''minimum recommended configuration'' |
|
Line 114: | Line 152: |
1. Review pricing vs. Hydro-2013 survey results | |
Line 127: | Line 166: |
1. Review finances & ensure funding to mid-2014 |
V2 ToDo List
High-Priority Goals
Complete final V2 MVA features & configuration
Get V2 into the hands of reviewers
Deliver to first paying customer
Planning
AH/JK - agree JK tasks/priorities & write up in JK Work Schedule wiki page - highest priority
JK - update V2UsabilityReview wiki page - high priority
Review & update V2LaunchPlan - lower priority
Upcoming Working Sessions: 04 to 15 November 2013
Define releases - AH/JK by phone based on notes to be supplied by JK (AH/JK 2013-11-05, Tue at 11:30). Proposed releases
R1 - Organizing and sharing
R2 - Structure Collaboration
R3 - Project Management
R4 - Scheduling
Usability review - AH/JK working separately:
AH to supply list of recently updated items
AH to update JK v2p0 system (http://v2.softxs.ch/v2p0-jk) with latest software
JK to review V2UsabilityReview wiki page & own notes and compare with current software
JK to supply complete replacement for V2UsabilityReview wiki page (keeping TN notes)
AH/JK to diScuss any complex or unsatisfactory items & set priorities
Develop demo scenarios & write end-user documentation
- Scoping statement, for each proposed demo system
- Make list of demo systems to produce (smaller demos, drawing manager, meeting manager, site investigations)
- Make list of important transactions to demonstrate
Prioritize list & do the first n items
- Update (minimum required) demo configuration and configure demo accordingly
- Create demo data
- write up user instructions/documentation
- Scoping statement, for each proposed demo system
User roles & project structure design - Schedule AH/JK working session (mid/late this week?)
Infrastructure
- Setup 8-core Intel rack-mount server to replace existing zg-3 server
Memory upgrade: Determine what SIMMs to buy & order 32 GB memory (approx. 400 CHF)
Install Ubuntu 12.04.3 LTS Server
- Setup 2 x 4TB mirrored disks
Install VirtualBox & Vagrant
- Setup basic VMs
rinetd port forwarder
- Gateway system
- Web server for zg-3.softxs.ch
- Setup packet filter?
Setup VM suitable for hosting DrawMGT
- Install rackmount server in Datawire data center in Cham
Bring back existing zg-3server, which has 8-cores & 12 GB main memory
- Migrate all existing services from zg-1 server onto VMs on zg-3 server
- Setup old zg-3 server just like new one, for replacing current zg-1 server
- Complete implementation of Puppet-managed DNS for DMZ
Concept & design for monitoring
Deployment & Operations
- Setup automated backups for www.softxs.ch: documents and database
- Setup automated database reset for demo.softxs.ch/hydro
- Implement deployment of event daemon cronjobs
- Implement deployment of backup jobs
- Implement deployment of log rotation jobs
Look into Google (or other) web analytics JK
Test VM-based V2 deployment, currently implemented for FreeBSD, to ensure it works with Ubuntu
- Setup email on az-1 server
Look into backups at Amazon & Google
Look into style guide for web site
MAPS System
- Complete Six-payments interface
- Review user management to check if any updates are required
- Implement skeleton for V2 deployment daemon
- Complete implementation of Questionnaire module
- Implement display of audit trail, investigate online analytics
V2 Application
Planning & Specification
- List of V2 features to fix/improve - Final check of Usability review
Workflow & User Role working paper in preparation for working session
- Prioritized list of next V2 features to implement.
- Design/rework of user roles as specified by JK
- Final review of multi-file uploads
- Decision/design of incoming transmittals
- Design of workflows
- Design of reporting
- Design of project management structures
Coding
- User Management
- Ability to manage external users. E.g. transmittal recipients
- External users will not be registered in MAPS
- All users with logins will be registered in MAPS
- Ability to enable/disable internal and external users
- Ability to put users into folders to allow delegation user management
- Ability to manage external users. E.g. transmittal recipients
- Implement display of audit trail
Testing
- Make a list of what application areas do not have automated testing
Review
- Transmittals
- Front-end GUI
- Transmittal email
- File handling
- Final check of Usability Review
- Requirements for Pöyry Uma Oya system (first V2 customer)
- Review if all necessary 'delete' transactions are completed
- Review to check if all back links and cancel buttons have been removed
Web Site
Review for spelling & grammar errors & make corrections
AH - Install new Features web page text - high priority
- PM Handbook
- Complete PM outline
- Identify initial chapters to work on
- Start writing chapters
Configuration handbook - part of PM Handbook? Priority?
- Configuration checklist
Quickstart Guide - part of PM Handbook? Priority?
Install specification draft - lower priority
Write some news articles - lower priority
Outline for a webcast - lower priority
Demo Systems
Final updates to Hydro demo - JK
- Final tuning of WBS
Complete minimum recommended configuration
- More documentation for Hydro demo
- Define what documentation is needed
- Implement Engineering Collaboration demo
- Implement Proposal Preparation demo
Sales & Marketing
- Follow-up on Tokyu offer
- Prepare offer for Aegir for Sisimiut archive system
- Review pricing vs. Hydro-2013 survey results
V2 System Trials
- Emails to trial system reviewers
- Robert Bartlett
- Aegir Johannsson
- Harald Schmitt
- Anthony Sullivan
Administration
- Determine when to sign-up for Six payments
- Write up terms and conditions (AGB)
Review finances & ensure funding to mid-2014