Itr1_Minimum Viable Product (MVP) - talshi/Yerushalmit GitHub Wiki
Iteration Goals
- Familiarity with PHP.
- Construction of the first page.
- Menu for Plugin on WordPress.
- Building the Classes: Map, Category, Activity according The class diagram.
Roles
- Scrum Master: talshi
Issues
Meeting Summary
-
GoDaddy's server establishment.
-
Building an admin panel for plugin.
-
Planning the template's design and future work on it.
-
Data of the old site has been backed up (as XML), and loaded to the new site.
Iteration Result
- We all invested our time to learn and practice PHP, especially in Wordpress environment.
- The first page of the plugin has been built. The preview was uploaded to server.
- Menu has added to Wordpress dashboard.
- We started to build the classes (Map, Category, Activity), but there are still changes to do.
The main functionallity which achieved in this iteration is the ability to upload a photo by using wordpress media uploader. The organization team will can use the plugin to do that simplicity thanks to responsive and simple UI which was also built in this iteration.
Team Cooperation
We splited to small teams and pairs, when one supports the other. We merged changes and seperated work after all teams have done.
Tasks Status
Everything has done for iteration 1, we are still planning the next iterations. It must say that changes always present, therefore it is hard to stick the plan. We meet frequently to cooridinate change of plan and continuing work.
Points Summary
- Familiarity with PHP - 13 points
- Building the Class Activity - 10 points
- Building the Class Map - 8 points
- Building the Class Category - 8 pointes
- Upload image - 13 points
- Building wordpress menu - 8 points
Total: 60 points.
Iteration Conclusion
- We finished all issues for iteration 1 so far, and everything is on schedule.
- The product contains the basic elements, which meet the requirements.
- There are no tests for the product yet. we made basic and non-formal tests after adding a feature to ensure everything works as fine and everything worked as expected. We should plan and write formal tests and perform them when the product will be stable enough.
- Our product based on MVC, therefore the team is separated to client and server developers. We are satisfied from the division of labor and each teammate did what he needed to do as expected. There was a clear division of work and every teammate did his issues. We continue to work in this way for now.
- Daily interaction between teammates is done using Whatsup, Facebook and Gitter. We meet once a week at college.
- Unfortunately, relevant problems usually was found late and was needed urgent care. We make efforts that problems will be found earlier and at the relevant time.
- We evaluate all the evaluation points.
- Relevant risks for now:
- There is still risk of unfamiliar technologies, which we are expected to learn on the fly.
- The combination between two or more programming languages. We know there is a solution but we have to learn how to do it.
- The client is satisfied from the product so far.
Closed Issues
Demonstration:
-
Manage Map
-
Upload Image
Code review
Code review will be done according to the team separation, e.g client side and server side developers.
The client side developers will review the server side developers and and conversely.
From the point of view of client side developers, the server side developers worked well.
The client side developers noticed using non significant names for function once in a while but not usually.
Most of the fixes were delivered on the fly and immediately.
From the point of view of the server side developers, fixes and changes that connected to the server side functionality and significant for the work were delivered immediately.
Testing
Local tests only.
Unit tests was not written yet.
In the end of iteration 2 and from iteration 3 we will do more formal tests.