Differences between revisions 11 and 12
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
 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. Define releases - '''AH/JK''' by phone based on notes to be supplied by JK (AH/JK 2013-11-05, Tue at 11:30).
 1. Usability review - '''AH/JK''' working separately
Line 33: Line 24:
    * 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
Line 43: Line 28:
= Administration =

 1. Determine when to sign-up for Six payments
 1. Write up online purchase terms and conditions (AGB)
 1. Review finances & ensure funding to mid-2014

= Sales & Marketing =

 1. Follow-up on Tokyu offer
 1. Prepare offer for Aegir for Sisimiut archive system
 1. Review pricing in light of Hydro-2013 survey results

= Web Site =

 1. Review web pages for spelling & grammatical mistakes & make corrections - '''AH'''
 1. Install new ''Features'' web page text - '''AH'''
 1. ''PM Handbook'' - '''JK'''
    1. PM Handbook to be composed of three parts:
       1. ''Project Management'' - General, not V2 specific
       1. ''User's Guide to Works Organiser''
       1. ''Configuration Handbook'' - including a ''Configuration Checklist''
    1. Complete PM outline
    1. Identify initial chapters to write
    1. Start writing chapters
    1. Will there be ''Quickstart Guide'' as part of the PM Handbook? - ''priority?''
 1. Look into Google (or other) web analytics - '''JK'''

== Demo Systems ==

 1. Define ''Scoping Statement'' for each proposed demo system - '''JK'''
    1. Make prioritized list of demo systems to produce. Proposed list:
       1. ''Engineering Team Collaboration''
       1. ''Proposal Preparation''
       1. ''Metro system''
       1. ''Drawing Manager''
       1. ''Meeting Manager''
       1. ''Site Investigations''
    1. Make list of important transactions to demonstrate
    1. Demo system implementation:
       1. Update (minimum required) demo configuration and configure demo accordingly
       1. Create demo data
       1. Write up user instructions/documentation
 1. Final updates to Hydro demo - '''JK'''
    1. Final tuning of WBS
    1. Complete ''minimum recommended configuration''
 1. More documentation for Hydro demo - '''JK'''
    1. Define what documentation is needed
 1. Implement Engineering Collaboration demo - '''JK'''
 1. Implement Proposal Preparation demo - '''JK'''

== V2 System Trials ==

 1. Emails to trial system reviewers - '''AH'''
    1. Robert Bartlett
    1. Aegir Johannsson
    1. Harald Schmitt
    1. Anthony Sullivan
 1. Consider getting reviewers to assist creating example configurations

= MAPS System =

 1. Complete Six-payments interface - '''DS'''
 1. Review user management to check if any updates are required
 1. Implement skeleton for V2 deployment daemon - '''AH'''
 1. Complete implementation of Questionnaire module - '''AH'''
 1. Implement display of audit trail - '''AH'''
    1. Investigate Google analytics?

= V2 Application =

== Design & Specification ==

 1. Define future releases - '''AH/JK'''
    1. Prioritized list of next V2 features to implement
    1. Proposed releases:
       * '''R1 - Organizing and Sharing'''
       * '''R2 - Structured Collaboration'''
       * '''R3 - Project Management'''
       * '''R4 - Scheduling'''
 1. Final list of V2 features to fix/improve before release:
    * '''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 agianst 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. ''Workflow & User Role'' working paper in preparation for working session - '''JK'''
 1. Requirements for Pöyry Uma Oya system (first V2 customer)
 1. Design/rework of user roles as specified in V2UsabilityReview - '''AH/JK'''
 1. Decision/design of incoming transmittals - '''AH/JK'''
 1. Design of project management structures - ''low priority''

== Review ==

 1. Review proposed user management - '''JK'''
 1. Transmittals - '''JK'''
    1. Front-end GUI
    1. Transmittal email
 1. Final review of multi-file uploads - '''JK'''
 1. Review if all necessary 'delete' transactions are completed - '''AH/TN'''
 1. Review to check if all back links and cancel buttons have been removed - '''AH/TN'''

== Coding ==

 1. User Management - '''TN'''
    1. Ability to manage external users. E.g. transmittal recipients
       1. External users will not be registered in MAPS
       1. All users with logins will be registered in MAPS
    1. Ability to enable/disable internal and external users
    1. Ability to put users into ''org chart'' to allow delegation user management
 1. Implement display of audit trail (mainly for transmittal downloads) - '''TN'''

== Testing ==

 1. Make a list of what application areas do not have automated testing - '''TN'''
 1. Prioritize list for implementing additional testing - '''AH/TN'''
 1. Implement additional testing - '''TN'''
Line 45: Line 147:
 1. Setup 8-core Intel rack-mount server to replace existing zg-3 server  1. Setup 8-core Intel rack-mount server to replace existing zg-3 server - '''AH'''
Line 56: Line 158:
 1. Install rackmount server in Datawire data center in Cham  1. Install rackmount server in Datawire data center in Cham - '''AH'''
Line 58: Line 160:
 1. Migrate all existing services from zg-1 server onto VMs on zg-3 server
 1. Setup old zg-3 server just like new one, for replacing current zg-1 server
 1. But AWS EC2 micro image for a year and see if performance is significantly better than free tier
 1. Complete implementation of Puppet-managed DNS for DMZ
 1. Monitoring prototype
 1. Migrate all existing services from zg-1 server onto VMs on zg-3 server - '''AH/TN'''
 1. Setup old zg-3 server just like new one, for replacing current zg-1 server - '''AH'''
 1. Buy AWS EC2 micro image for a year and see if performance is significantly better than free tier - '''AH'''
 1. Complete implementation of Puppet-managed DNS for DMZ - '''AH'''
 1. Monitoring prototype - '''AH'''
Line 66: Line 168:
 1. Setup automated backups for www.softxs.ch: documents and database
 1. Setup automated database reset for demo.softxs.ch/hydro
 1. Implement deployment of event daemon cronjobs
 1. Implement deployment of backup jobs
 1. Implement deployment of log rotation jobs
 1. Look into Google (or other) web analytics '''JK'''
 1. Test VM-based V2 deployment, currently implemented for Free``BSD, to ensure it works with Ubuntu
 1. Setup email on az-1 server
 1. Look into backups at Amazon & Google
 1. Look into ''style guide'' for web site
 

= MAPS System =

 1. Complete Six-payments interface
 1. Review user management to check if any updates are required
 1. Implement skeleton for V2 deployment daemon
 1. Complete implementation of Questionnaire module
 1. Implement display of audit trail, investigate online analytics

= V2 Application =

== Planning & Specification ==

 1. List of V2 features to fix/improve, including final check of V2UsabilityReview
 1. ''Workflow & User Role'' working paper in preparation for working session - '''JK'''
 1. Prioritized list of next V2 features to implement - '''AH/JK'''
 1. Review proposed user management - '''JK'''
 1. Design/rework of user roles as specified in V2UsabilityReview - '''AH/JK'''
 1. Final review of multi-file uploads - '''JK'''
 1. Decision/design of incoming transmittals - '''AH/JK'''
 1. Design of workflows - ''lower priority''
 1. Design of reporting - ''lower priority''
 1. Design of project management structures - ''lower priority''

== Coding ==

 1. User Management
    1. Ability to manage external users. E.g. transmittal recipients
       1. External users will not be registered in MAPS
       1. All users with logins will be registered in MAPS
    1. Ability to enable/disable internal and external users
    1. Ability to put users into ''org chart'' to allow delegation user management
 1. Implement display of audit trail

== Testing ==

 1. Make a list of what application areas do not have automated testing

== Review ==

 1. Transmittals
    1. Front-end GUI
    1. Transmittal email
 1. File handling
 1. Final check of Usability Review
 1. Requirements for Pöyry Uma Oya system (first V2 customer)
 1. Review if all necessary 'delete' transactions are completed
 1. Review to check if all back links and cancel buttons have been removed

= Web Site =

 1. Review web pages for spelling & grammatical mistakes & make corrections
 1. '''AH''' - Install new ''Features'' web page text - ''high priority''
 1. ''PM Handbook''
    1. PM Handbook in three parts:
       1. ''Project Management'' - General, not V2 specific
       1. ''User Guides to Works Organiser''
       1. ''Configuration Handbook'' - With a ''Configuration Checklist''

    1. Complete PM outline
    1. Identify initial chapters to work on
    1. Start writing chapters
    1. Will there be ''Quickstart Guide'' as part of the PM Handbook? - ''priority?''
 1. Install specification draft - ''lower priority''
 1. Write some ''news articles'' - ''lower priority''
 1. Outline for a webcast - ''lower priority''

== Demo Systems ==

 1. Final updates to Hydro demo - '''JK'''
    1. Final tuning of WBS
    1. Complete ''minimum recommended configuration''
 1. More documentation for Hydro demo
    1. Define what documentation is needed
 1. Implement Engineering Collaboration demo
 1. Implement Proposal Preparation demo

= Sales & Marketing =

 1. Follow-up on Tokyu offer
 1. Prepare offer for Aegir for Sisimiut archive system
 1. Review pricing vs. Hydro-2013 survey results

== V2 System Trials ==

 1. Emails to trial system reviewers
    1. Robert Bartlett
    1. Aegir Johannsson
    1. Harald Schmitt
    1. Anthony Sullivan

= Administration =

 1. Determine when to sign-up for Six payments
 1. Write up terms and conditions (AGB)
 1. Review finances & ensure funding to mid-2014
 1. Setup automated backups of for documents & database ''www.softxs.ch'' - '''AH'''
 1. Setup automated database reset for ''demo.softxs.ch/hydro'' - '''AH'''
 1. Setup email on ''az-1.softxs.ch'' server - '''AH'''
 1. Test VM-based V2 deployment on Ubuntu-based hosts - '''AH'''
    1. Currently implemented for VMs on Free``BSD
 1. Implement additional deployment tasks: - '''AH'''
    1. Event daemon cronjobs
    1. Backup jobs
    1. Log rotation jobs

V2 ToDo List

V2Master

High-Priority Goals

  1. Complete final V2 MVA features & configuration

  2. Get V2 into the hands of reviewers

  3. Deliver to first paying customer

Planning

  1. AH/JK - agree JK tasks/priorities & write up in JK Work Schedule wiki page - highest priority

  2. JK - update V2UsabilityReview wiki page - high priority

  3. Review & update V2LaunchPlan - lower priority

Upcoming Working Sessions: 04 to 18 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).

  2. Usability review - AH/JK working separately

  3. Develop demo scenarios & write end-user documentation

  4. User roles & project structure design - Schedule AH/JK working session (mid/late this week?)

  5. Design of incoming transmittals

Administration

  1. Determine when to sign-up for Six payments
  2. Write up online purchase terms and conditions (AGB)
  3. Review finances & ensure funding to mid-2014

Sales & Marketing

  1. Follow-up on Tokyu offer
  2. Prepare offer for Aegir for Sisimiut archive system
  3. Review pricing in light of Hydro-2013 survey results

Web Site

  1. Review web pages for spelling & grammatical mistakes & make corrections - AH

  2. Install new Features web page text - AH

  3. PM Handbook - JK

    1. PM Handbook to be composed of three parts:
      1. Project Management - General, not V2 specific

      2. User's Guide to Works Organiser

      3. Configuration Handbook - including a Configuration Checklist

    2. Complete PM outline
    3. Identify initial chapters to write
    4. Start writing chapters
    5. Will there be Quickstart Guide as part of the PM Handbook? - priority?

  4. Look into Google (or other) web analytics - JK

Demo Systems

  1. Define Scoping Statement for each proposed demo system - JK

    1. Make prioritized list of demo systems to produce. Proposed list:
      1. Engineering Team Collaboration

      2. Proposal Preparation

      3. Metro system

      4. Drawing Manager

      5. Meeting Manager

      6. Site Investigations

    2. Make list of important transactions to demonstrate
    3. Demo system implementation:
      1. Update (minimum required) demo configuration and configure demo accordingly
      2. Create demo data
      3. Write up user instructions/documentation
  2. Final updates to Hydro demo - JK

    1. Final tuning of WBS
    2. Complete minimum recommended configuration

  3. More documentation for Hydro demo - JK

    1. Define what documentation is needed
  4. Implement Engineering Collaboration demo - JK

  5. Implement Proposal Preparation demo - JK

V2 System Trials

  1. Emails to trial system reviewers - AH

    1. Robert Bartlett
    2. Aegir Johannsson
    3. Harald Schmitt
    4. Anthony Sullivan
  2. Consider getting reviewers to assist creating example configurations

MAPS System

  1. Complete Six-payments interface - DS

  2. Review user management to check if any updates are required
  3. Implement skeleton for V2 deployment daemon - AH

  4. Complete implementation of Questionnaire module - AH

  5. Implement display of audit trail - AH

    1. Investigate Google analytics?

V2 Application

Design & Specification

  1. Define future releases - AH/JK

    1. Prioritized list of next V2 features to implement
    2. Proposed releases:
      • R1 - Organizing and Sharing

      • R2 - Structured Collaboration

      • R3 - Project Management

      • R4 - Scheduling

  2. Final list of V2 features to fix/improve before release:
    • 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 agianst 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

  3. Workflow & User Role working paper in preparation for working session - JK

  4. Requirements for Pöyry Uma Oya system (first V2 customer)
  5. Design/rework of user roles as specified in V2UsabilityReview - AH/JK

  6. Decision/design of incoming transmittals - AH/JK

  7. Design of project management structures - low priority

Review

  1. Review proposed user management - JK

  2. Transmittals - JK

    1. Front-end GUI
    2. Transmittal email
  3. Final review of multi-file uploads - JK

  4. Review if all necessary 'delete' transactions are completed - AH/TN

  5. Review to check if all back links and cancel buttons have been removed - AH/TN

Coding

  1. User Management - TN

    1. Ability to manage external users. E.g. transmittal recipients
      1. External users will not be registered in MAPS
      2. All users with logins will be registered in MAPS
    2. Ability to enable/disable internal and external users
    3. Ability to put users into org chart to allow delegation user management

  2. Implement display of audit trail (mainly for transmittal downloads) - TN

Testing

  1. Make a list of what application areas do not have automated testing - TN

  2. Prioritize list for implementing additional testing - AH/TN

  3. Implement additional testing - TN

Infrastructure

  1. Setup 8-core Intel rack-mount server to replace existing zg-3 server - AH

    1. Memory upgrade: Determine what SIMMs to buy & order 32 GB memory (approx. 400 CHF)

    2. Install Ubuntu 12.04.3 LTS Server

    3. Setup 2 x 4TB mirrored disks
    4. Install VirtualBox & Vagrant

    5. Setup basic VMs
      1. rinetd port forwarder

      2. Gateway VM
      3. Web server VM for zg-3.softxs.ch
    6. Setup packet filter?
    7. Setup VM suitable for hosting DrawMGT

  2. Install rackmount server in Datawire data center in Cham - AH

    1. Bring back existing zg-3server, which has 8-cores & 12 GB main memory

  3. Migrate all existing services from zg-1 server onto VMs on zg-3 server - AH/TN

  4. Setup old zg-3 server just like new one, for replacing current zg-1 server - AH

  5. Buy AWS EC2 micro image for a year and see if performance is significantly better than free tier - AH

  6. Complete implementation of Puppet-managed DNS for DMZ - AH

  7. Monitoring prototype - AH

Deployment & Operations

  1. Setup automated backups of for documents & database www.softxs.ch - AH

  2. Setup automated database reset for demo.softxs.ch/hydro - AH

  3. Setup email on az-1.softxs.ch server - AH

  4. Test VM-based V2 deployment on Ubuntu-based hosts - AH

    1. Currently implemented for VMs on FreeBSD

  5. Implement additional deployment tasks: - AH

    1. Event daemon cronjobs
    2. Backup jobs
    3. Log rotation jobs

V2ToDo (last edited 2013-12-10 15:25:25 by gw)

Copyright 2008-2014, SoftXS GmbH, Switzerland