Project plan - stacc-dasso/woocommerce-extension GitHub Wiki

Roles in project

  • Lauri Leiten
    • Team lead
    • Back end
  • Hannes Saariste
    • Front end
    • Help with back end
  • Stiivo Siider
    • Testing
    • Help with back end
  • Martin Jürgel
    • Documentation
    • Help with back end, testing

Communication means

  • At least a biweekly meeting with the customer, more often if necessary.
  • Slack
  • Discord
  • E-mail

Work process

How and using what materials the customer is going to understand what you are going to build

We will be discussing the project plan with the customer, they’ll also have access to our repository and during the biweekly meetings we will showcase and discuss what have we built and what are we working on.

How do you determine that the customer is accepting your solution proposal

Through feedback from the customer, from either online or in-person meetings. If the customer supports our proposal, we consider it as accepted.

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)

Tasks will be assigned by the team leader. Back end tasks will be mainly for Lauri, Stiivo and Martin. Hannes will look after the front end tasks, with Stiivo and Martin helping as needed. Progress will be documented and all challenges encountered along the way written down in the wiki as per the client's request.

Initial development of a feature will be done in a new local branch (feature branch). Unit tests for all new features will be written by the developer in charge of writing the feature. Once the developer wishes to merge their code into the dev branch, they will do a pull request. After this, the code will be reviewed by a team member and if approved, the code will be merged with the dev branch. At this point, the feature is considered "done" and ready to be demonstrated to the customer.

The dev branch will be merged with the master branch every time a milestone is reached - in our case, at the end of every iteration. Before merging, all team members must have looked at the code and given their approval.

When do you consider something ready to be published to the customer for review

As the customer will have access to our repository, they can review our work at any time. Other than that, everything that'll get merged to the dev branch will be ready for customer review.

How do you gather feedback from the customer and/or end users.

For the customer, we communicate online through Slack and Discord and have biweekly meetings where we show our work and ask for feedback.

What is the definition of DONE on a task

A task is done when it reaches the development branch and the customer has reviewed it.

Scope

Iteration 1

Iteration 2

Iteration 3

Iteration 4