-
Notifications
You must be signed in to change notification settings - Fork 0
Sprint 1
See the Meetings & Minutes page.
Here is the current (deployed) version of the Storefront Calendar website.
The summarized version of the estimates and priorities can be found here
The scrum board can be found in pdf format as exported by Trello.
PHP with the framework CodeIgniter was chosen because of member familiarity and recommendation. Other alternatives were using Django or some similar technology, it would however been new waters for every member. This resulted in us deciding on CodeIgniter for PHP. The architecture of the website uses the MVC model because it is enforced by CodeIgniter. It also allows different responsibilities for members so the work is divided into almost separate entities.
The product champion wants us to implement administrator user stories first, before implementing client or front-desk user stories. In fact, she said, she would be happy to just receive the final product just with administrator’s user stories implementation. However, we told the product champion that, the web-application would be really useful and beneficial if clients’ can use it too. We finally decided on implementing administrator, client, and front-desk. We also asked about their floor plan in order to know number of rooms and get rough idea about capacity of the room. We also have asked Product Champion to send email address of their IT department in order to know more about their website and the condition of their website since the website was down for one week. Proof that we have called
We have asked about the information that needed to be included in the database such as user’s information, client information. This will be implemented in sprint 3. The phone call was short and Product Champion asked us to email her in order to remind her about our request.
Here is the team Burndown Chart and the numbers are represented here Legend
