“The aim of Wimma Lab's 2018 activities is to unite the....”
“Enterprise X needs to develop the <object> project”
“The project will be implemented within the <ZZPP0100GrowthintoWorkingLifeExpert> course organized by the Institute of Information Technology of Jyväskylä University of Applied Sciences.”
> “Enterprise X needs to develop a solution for”
> “The project will be implemented within the XYZ> course organized by the Institute of Information Technology of Jyväskylä University of Applied Sciences.”
The object is often a broader concept than the actual task defined for the project. The object describes in a clear way, often based on a graphic representation, what kind of system entity or functionality the current project task will be part of. Thus, the current system and the client's current mode of operation are described here.
>The object is often a broader concept than the actual task defined for the project. The object describes in a clear way, often based on a graphic representation, what kind of system entity or functionality the current project task will be part of. Thus, the current system and the client's current mode of operation are described here.
## 1.2 Objectives and tasks
...
...
@@ -20,11 +19,10 @@ The object is often a broader concept than the actual task defined for the proje
* Produce a working demo (Proof Of Concept)
Define the main content of the work in this project; the task of the project is related to the entity described in the project object. <Whatistobedone?> / <Whatactivitiesaretobedevelopedandhow?><Visionofthefuturestate> / <Whatistheendresulttobeproduced(concrete)?> / <Whatarethepartialorintermediateresults?><Towhomistheresulttobeproduced?>” the task is to keep the various parties aware of the project situation. At the end of each phase, a phase report will be drawn up to inform the executive board of the progress of the project. "
>Define the main content of the work in this project; the task of the project is related to the entity described in the project object. <What is to be done?> / <What activities are to be developed and how?> <Vision of the future state> / <What is the end result to be produced (concrete)?> / <What are the partial or intermediate results?> <To whom is the result to be produced?>” the task is to keep the various parties aware of the project situation. At the end of each phase, a phase report will be drawn up to inform the executive board of the progress of the project. "
## 1.3 Delimitation and subscriptions
>Clarify the role of the project by delimiting the excluded parts of the target system or the overall project. The external factors that significantly limit the performance of the task should also be described separately.
>This also specifies the sets of tasks that are likely to be included in the current section at some point, but which will not be carried out within the framework of this project. Typical such tasks could be e.g. construction and training of the operating environment. Other restrictions could be, for example, the language used in the software interface.
...
...
@@ -68,19 +66,19 @@ Define the main content of the work in this project; the task of the project is
## Project team
“The project team will perform the tasks assigned to the project by the management team within the available resources. During the project, the roles of group leader and secretary will rotate within the group, with each team member acting once in each role. ”
>“The project team will perform the tasks assigned to the project by the management team within the available resources. During the project, the roles of group leader and secretary will rotate within the group, with each team member acting once in each role. ”
## Executive team
“The executive team consists of elected representatives of the project team, supervisors and the client. If necessary, other persons, e.g. experts, may also be invited to the meetings of the executive team. The composition of the executive team is presented in an attachment of the project agreement. ”
>“The executive team consists of elected representatives of the project team, supervisors and the client. If necessary, other persons, e.g. experts, may also be invited to the meetings of the executive team. The composition of the executive team is presented in an attachment of the project agreement. ”
## Support Group
The task of the support group is to give the project team substantive guidance on how to complete the task. The section should introduce other stakeholders of the project (customer, external consultants, etc.) at personal level. Any person(s) from the client organization who participate in the project should be introduced. At least name, contact information, job description and role in the project should be introduced for any person(s) from the client organization who participate in the project.
>The task of the support group is to give the project team substantive guidance on how to complete the task. The section should introduce other stakeholders of the project (customer, external consultants, etc.) at personal level. Any person(s) from the client organization who participate in the project should be introduced. At least name, contact information, job description and role in the project should be introduced for any person(s) from the client organization who participate in the project.
## 2.2 Responsibilities and decision-making process
This part describes the responsibilities of all members of the project organization (e.g. executive team, project manager, secretary, team, supervisors) as well as the decision-making process (e.g. the project manager prepares and presents any items to the executive team for decision…).
>This part describes the responsibilities of all members of the project organization (e.g. executive team, project manager, secretary, team, supervisors) as well as the decision-making process (e.g. the project manager prepares and presents any items to the executive team for decision…).
## 3 Time objectives of the project
...
...
@@ -112,43 +110,50 @@ This part describes the responsibilities of all members of the project organizat
> “The closure phase includes measures related to the completion of the project. During the phase, the project team prepares a final project report and a presentation to the executive team. During the phase, the result of the project will be handed over to the client, the last meeting of the executive team will be held in week X and the project organization will be dissolved. The final phase will result in a final report on the project. ”
```mermaid
gantt
title Project steps
dateFormat DD-MM-YYYY
section GANTT
Step 1 :active,k1,15-01-2019, 20-01-2019
Step 2 :active,k2,after k1, 20-02-2019
Step 3 :active,k3,after k2, 20-03-2019
Step 4 :active,k4,after k3, 20-04-2019
```plantuml
Project starts the 2021-5-15
[Project Active] Starts 2021-5-15 and ends 2021-8-15
[Requirement gathering] Starts 2021-5-15 and ends 2021-5-20
[Desing and planning] Starts 2021-5-20 and ends 2021-6-5
[Desing and implementation] Starts 2021-6-5 and ends 2021-7-15
[Testing and fixing] Starts 2021-7-16 and ends 2021-8-1
[Acceptance Testing] Starts 2021-8-1 and ends 2021-8-10
[Delivery] Starts 2021-8-10 and ends 2021-8-15
```
## 4 Quality management
Working methods, tools, instructions and standards applicable to the project.
>Working methods, tools, instructions and standards applicable to the project.
This section lists all the methods, tools, and standards used with their version numbers. Often, the client has some method that the project team should follow. The client can also specify the document layout standards to be followed. Otherwise, the project team will tailor a suitable one from the templates provided by the IT Institute and get it approved by the client.
The course sets certain requirements for project monitoring tools and reporting, which should be taken into account. However, the course does not force a certain way to use the tools, so it is worth making a plan for their use at this point.
The basics of project information and version control need to be clarified so that all project stakeholders know the location of the latest versions of documents. There will be several versions of the project plan and all other key documents of the project, to which version history must be added in order to be able to follow the progress of the project afterwards. If an individual piece of hardware or software rises to a critical position in terms of project implementation, it is a good idea to appoint a responsible person from within the team. The person should be familiar with the device or software, if possible. Below is a list of things to plan and document:
### 4.1 Procedure for approving interim and final results
The approval procedure that has been agreed in the project is recorded here.
>The approval procedure that has been agreed in the project is recorded here.
### 4.2 Change Management
Describe the change management procedure for changes related to project policies or project results.
>Describe the change management procedure for changes related to project policies or project results.
### 4.3 Documentation
Write down where the documents are stored / archived, how they are distributed and who is responsible for the different documents.
>Write down where the documents are stored / archived, how they are distributed and who is responsible for the different documents.
### 4.4 Risk management
List the risks, assess their severity and probability, and try to consider measures on how the most serious / probable risks could be prevented in advance. In addition, it would be good to have a plan of how to act if the risk materializes.
>List the risks, assess their severity and probability, and try to consider measures on how the most serious / probable risks could be prevented in advance. In addition, it would be good to have a plan of how to act if the risk materializes.
Attach the following section here: Risk Management Table
### 4.5 Review Policy
List and tentatively schedule project performance reviews based on the prepared implementation plan. List the reviews that will be held, the tentative date, the issues to be addressed, the participants, and the practices for delivering the review material (what, when, how).
>List and tentatively schedule project performance reviews based on the prepared implementation plan. List the reviews that will be held, the tentative date, the issues to be addressed, the participants, and the practices for delivering the review material (what, when, how).
Links to review protocol documents.
### 4.6 Plans to supplement the project plan
This section indicates which additional plans are available or will be developed during the project (e.g. communication, risk management, testing and deployment plan).
>This section indicates which additional plans are available or will be developed during the project (e.g. communication, risk management, testing and deployment plan).
* Requirement specification?
* Risk Management plan
...
...
@@ -156,35 +161,44 @@ This section indicates which additional plans are available or will be developed
* Official sources?
## 4.7 Dates for reviewing and updating plans
>The project plan responds to anomalies and environmental changes, so it is updated during the project. The points at which the timelines of the plan must at least be checked are recorded here.
### 4.7 Dates for reviewing and updating plans
The project plan responds to anomalies and environmental changes, so it is updated during the project. The points at which the timelines of the plan must at least be checked are recorded here.
### 4.8 Project Suspension Criteria
Any real-life project plan also includes project termination criteria. However, these are not used in student projects because the projects use a certain number of hours to produce the result and the result is handed over as it is at the end of the course. However, the project team will make a further development plan from which a possible new project will continue.
## 4.8 Project Suspension Criteria
>Any real-life project plan also includes project termination criteria. However, these are not used in student projects because the projects use a certain number of hours to produce the result and the result is handed over as it is at the end of the course. However, the project team will make a further development plan from which a possible new project will continue.
## 5 Communication and monitoring of project progress (communication plan)
List the workspaces and communication tools agreed in the project, meeting policy and communication, reporting and information.
>List the workspaces and communication tools agreed in the project, meeting policy and communication, reporting and information.
## 6 End of the project
### 6.1 Delivery, commissioning of the final product
The end product of the project must also be documented at a reasonable level. The end product may include commissioning training for the customer and possibly an installation or commissioning service. If the role of the training in the project is significant (for example, the users of the software have not been involved in the project and do not know how the system works) the project plan must be accompanied by a plan for the training to be provided to the client. In addition, if necessary, the project plan must also be accompanied by an installation plan and a commissioning plan.
## 6.1 Delivery, commissioning of the final product
>The end product of the project must also be documented at a reasonable level. The end product may include commissioning training for the customer and possibly an installation or commissioning service. If the role of the training in the project is significant (for example, the users of the software have not been involved in the project and do not know how the system works) the project plan must be accompanied by a plan for the training to be provided to the client. In addition, if necessary, the project plan must also be accompanied by an installation plan and a commissioning plan.
### 6.2 Recording, archiving and retention period of material produced by the project
"The rest of the project team's documentation for the IT Institute is stored in GitHub." The client should clearly define which documents can be left as lessons for subsequent projects. Typically, the various plans and the final report are such documents.
## 6.2 Recording, archiving and retention period of material produced by the project
>"The rest of the project team's documentation for the IT Institute is stored in GitHub." The client should clearly define which documents can be left as lessons for subsequent projects. Typically, the various plans and the final report are such documents.
### 6.3 Formal closure of the project
It is important to determine when, where or how the project will end. A project decision can be a specific date, a certain degree of product readiness, a certain number of hours worked, a certain amount of money spent when a client adopts a product, the warranty period has expired, or when a client accepts a product.
## 6.3 Formal closure of the project
>It is important to determine when, where or how the project will end. A project decision can be a specific date, a certain degree of product readiness, a certain number of hours worked, a certain amount of money spent when a client adopts a product, the warranty period has expired, or when a client accepts a product.
* “The project ends dd.mm.yy, if…”
* "The project ends on dd.mm.yy, when the project agreement expires."
### 6.4 Closing Seminar
Usually projects are closed at a joint closing seminar. The participants and the time are recorded here.
## 6.4 Closing Seminar
>Usually projects are closed at a joint closing seminar. The participants and the time are recorded here.
### 6.5 Final report
The final report of the project will be prepared by the last meeting of the executive team.
## 6.5 Final report
>The final report of the project will be prepared by the last meeting of the executive team.
## Attachments
Any plans supplementing the project plan are attached here.
>Any plans supplementing the project plan are attached here.
