| Risk |
likelihood of occurrence |
Steps to reduce risk |
Response |
Severity |
| The customer will be unhappy with the initial phase of the app and we will have to make significant changes or even start over. |
Medium |
We will be in direct contact with the client and we will verify his satisfaction during every step of the design and implementation. |
We will set up a meeting with the client so we can better understand what exactly needs to be changed and how we can better meet his needs. |
High |
| Working with new tools in an unfamiliar environment can cause development to take longer as time is needed to learn everything. |
High |
We will spend a lot of time learning about the tools we will use prior to the developing phase in order to come prepared for the job. |
We will study and prepare as much as we can as well as get help and advice from others who are familiar with the tools we will be using. |
Low |
| Not enough storage space on the server |
Low |
We will calculate the approx. size and try to estimate it before we begin.
|
We will see if there is data we can compress. |
Medium |
| The customer wants additional features later, once development is already underway. |
Medium |
We will clarify the features at every stage for the client and we will make sure that they are sufficient. |
We will discuss and figure out what features are needed, and if the new requests are necessary we will see if there is a way to add them. |
Medium |
| Delay in schedule |
Medium |
We will schedule meetings at least once a week, so the total pace can be measured. After the meeting, another meeting will be scheduled |
We will schedule additional weekly meetings if there is a backlog. |
Medium |