The aim of the planned preventive maintenance is to mitigate the consequences of a software failure before occurs. Improving and replacing worn components before they fail. These are the Administration preventive maintenance activities that are going to be developed. The aim of this maintenance is to avoid or mitigate the consequences of failure or improving existing capabilities which require a more efficient approach.
Preventive maintenance activities focused on the SharePoint technical component. Improving this component, the Product owner will have a better access to the management of the user accounts. It will be easier to remove a user or change the role and also we could check the last login of each user.Five work packages (categories) have been created in order to clasify all the tasks:
- Content management
- User Uptake
- Project Management
- Helpdesk (Corrective Manteinance, not for planned tasks)
- Task: Only for planned parent tasks, registered like activities at the WBS. (e.g. 1.1 Administration preventive maintenance)
- Feature: For planned subtask, planned tasks (e.g. 1.1.1 Site maintenance and management in SharePoint)
- 1st Milestone (March-April)
- 2nd Milestone (May-Jun)
- 3rd Milestone (Jul-Aug)
- 4th Milestone (Sep-Oct)
- 5th Milestone (Nov-Dic)
- 6th Milestone (Jan-Feb)
And the following workflow (status):
- New: New task/feature. The work has not been started, so the % Done is 0. Is under one of the four categories (Operation, Content management, User Uptake, Project Management) and it will be assigned to the technician that is going to perform the task/feature. The feature is always linked to a parent task and under a milestone.
- In Progress: The feature is in progress, so the % Done is >0. Add Notes in the feature/task (problems, solutions, interesting information...). The task % Done is automatically updated while the child features are performed.
- Need Clarifications: Use this status if clarifications are needed (from the analyst, product owner...). Assign the feature and write the question in the Notes.
- On Hold: Use this status if the feature/task is locked and cannot be continued. Write the reason in the Notes. Done <%100 (as needed).
- Acceptance Demo: Use this status only if the feature or task have to be reviewed or tested (software developments/documentation). Assign the feature/task to testing manager/technical reviewer. Add comments. In case of software developments Done=%100 when the feature is deployed at the staging environment.
- To be deployed: The task or feature has been successfully tested by the testing team. Task or feature to be deployed in production environment.
- Closed: Done = %100. In case of software developments, the software has to be deployed at the production environment.
- Invalid: Task/Feature not valid. Done = %100. Add the reasons in Notes.