This wiki has had no edits or log actions made within the last 45 days and has been automatically marked as inactive. If you would like to prevent this wiki from being closed, please start showing signs of activity here. If there are no signs of this wiki being used within the next 15 days, this wiki will be closed in accordance to the Dormancy Policy (which all wiki founders accept when requesting a wiki). If this wiki is closed and no one reopens it 135 days from now, this wiki will become eligible for deletion. Note: If you are a bureaucrat, you can go to Special:ManageWiki and uncheck "inactive" yourself.Implementation: Difference between revisions
Content added Content deleted
Michaeldakin (talk | contribs) No edit summary |
Michaeldakin (talk | contribs) No edit summary |
||
| Line 22: | Line 22: | ||
** Menus |
** Menus |
||
** Security Mangagement |
** Security Mangagement |
||
==Phases and Timescales== |
|||
== |
|||
* Requirements |
|||
** Define (who, what, when) |
|||
** Timescale |
|||
* Design |
|||
** Define |
|||
** Timescale |
|||
* Build |
|||
** Define |
|||
** Timescale |
|||
* Testing |
|||
** Define players |
|||
** Timescale |
|||
* Go-live |
|||
** Define (cookbook etc) |
|||
** Timescale |
|||
NOTES: |
|||
# No phase happens in isolation. This must be conveyed to the customer. While gathering requirements we will be designing the solution |
|||
# We need to ascertain all elements - migration required? Year end considerations |
|||
=Pricing= |
=Pricing= |
||
| Line 31: | Line 49: | ||
*Completed testing 20% |
*Completed testing 20% |
||
*Go-live 30% |
*Go-live 30% |
||
=Naming= |
=Naming= |
||
| Line 38: | Line 55: | ||
| ⚫ | |||
* Bringing in external resource if required - how? |
|||
* platform provider |
|||
* Laszlo / Michael business arrangements - how do we work it? |
|||
* Who leads on what areas |
|||
* Laszlo time management - not impact his core business |
|||
* Brexit risk |
|||
* Language management |
|||
=Immediate action items= |
|||
| ⚫ | |||
* understand language translation software |
|||
* Sort solution to security |
|||
* Always lands on main page when logging in - how to handle? |
|||
Revision as of 12:24, 24 February 2019
Project Management
- Tools
- Ways of working
Project Phases
Preparation
- Statement of Work
- Contract
- Understand AS-IS
- Outline design of TO-BE
- Software Name
- Software components
- Wiki frontend?
- Cargo
- LUA
- HTML (through widgets)
- Javascript
- Excel
- SQL (external to Wiki)
- Design principles
- Boilerplate design
- Menus
- Security Mangagement
Phases and Timescales
- Requirements
- Define (who, what, when)
- Timescale
- Design
- Define
- Timescale
- Build
- Define
- Timescale
- Testing
- Define players
- Timescale
- Go-live
- Define (cookbook etc)
- Timescale
NOTES:
- No phase happens in isolation. This must be conveyed to the customer. While gathering requirements we will be designing the solution
- We need to ascertain all elements - migration required? Year end considerations
Pricing
Charging phases
- Contract sign-off 30%
- Build phase 20%
- Completed testing 20%
- Go-live 30%
Naming
- What do we call the product?
- How much do we cover up Wiki element
Ways of Working
- Bringing in external resource if required - how?
- platform provider
- Laszlo / Michael business arrangements - how do we work it?
- Who leads on what areas
- Laszlo time management - not impact his core business
- Brexit risk
- Language management
Immediate action items
- understand language translation software
- Sort solution to security
- Always lands on main page when logging in - how to handle?