Project plan - SuperTurban/ekm_mobiilposm2ng GitHub Wiki
Roles
- Tambet
- Client interactions
- Project lead: web application
- Project management
- Testing
- Documentation
- Meeri
- Documentation
- Testing
- Code verifying
- Kuldar
- Project lead: general and mobile app
- Back-end code
- System administration
- Joel
- Design
- Front-end code
- UX
Communication means
- In-house communication: Facebook, Skype and regular meetups if agreed beforehand.
- Client communication: Email, Skype and regular meetups.
Planned talks/meetups with the client
- 24.09.2017 Skype talk protocol
- 27.09.2017 meetup protocol
- 16.10.2017 meetup protocol
- 15.11.2017 Skype talk protocol
- 23.11.2017 meetup for mobileapp demo protocol
- 16.12.2017 Skype talk protocol
- Next meetup 21.12 at 10:00
Work processes
How and using what materials the customer is going to understand what you are going to build?
- We will show and explain the customer what we have done before the end of each iteration.
- Customer has some hands-on experience by designing the web page application with draw.io or another similar program.
How do you determine that the customer is accepting your solution proposal?
- After setting up system requirements and project vision, we meet up with the client and ask for verification. We will discuss our solution with the client and take notes from them in case there are proposals from the client that were not brought up in the first interview.
- If any functionalities are finished, we ask for the feedback in order to keep on track.
- We will ask client questions regularly in case we come across any while implementing the system.
How you are internally going to build the accepted solution (who assigns the tasks, who is going to implement it, will the tests be written, will code be reviewed, who is going to verify, who is doing the validation, etc)?
- There is going to be a project lead for the web (Tambet) and the Android (Kuldar) application development.
- The project lead (Kuldar) is going to assign tasks.
- All 4 team members will take part in developing the system.
- The team member who is assigned a task is responsible for getting it done.
- The assignee can ask questions from any other team members in case they run into difficulties.
- All the code will be reviewed (Meeri) and verified by the project lead (Kuldar).
- The code will be published for customer verification.
When do you consider something ready to be published to the customer for review?
- A functionality is ready to be published when all team members have tested it and verified it.
- A functionality is ready to be published if all other functionalities that it depends on, have been implemented.
How do you gather feedback from the customer and/or end users?
- During the regular meetups we will confirm whether the customer is satisfied thus far
- We will notify the customer after every release and send a description what functionalities we have added.
- The customer lets us know what functionalities are working according to the plan and his/her specifications.
- The first versions of the app are tested by the team members and the customer.
- The later versions of the app are tested by the friends of the team to get additional info from PHOSITAs.
What is the definition of DONE on a task?
- The functionality works as expected.
- The functionality is manually tested by all team members and the customer.
- The functionality is up on the server.