-
Notifications
You must be signed in to change notification settings - Fork 1
4. Development Methodology
| Date | Version | Description | Responsible |
|---|---|---|---|
| 16/03/2016 | 0.1.0 | Starting the document | Victor Arnaud |
| 18/03/2016 | 1.0.0 | Finalizing the document | Victor Arnaud |
| 18/03/2016 | 1.1.0 | Translating the document | Victor Arnaud |
- Methodology used.
- Sprint duration.
- Sprint Management.
- Events.
- Role.
- Pair Programming.
- Monitoring progress toward goal.
- Code Coverage.
For the constant improvement of the project, the execution was done following the agile methodology to increase the productivity and efficiency of the same.
We adapt SCRUM and XP for project development and management.
The duration of the sprint will be 2 weeks
The management of the sprint will be done by kanban cadres, in which we will have 4 main frames, the kanbans is in the project link (kanban of documentation) and Boards (kanban of development) of github:
Boards (Development kanban)
- New issues: New issues added
- icebox: Issues or features that are out of scope
- Product Backlog: All the functionalities that will be implemented in the project
- Sprint Backlog: Are the features that will be implemented in sprint
- Review: Features that need to be tested and revised according to the style sheet
- Done: Completed features
Project (Documentation kanban)
- Pending: Documentation not started
- In progress: Documentation that is still being done
- Done: Documentation completed
Note: The frame is generated by the Zenhub tool. To be able to view the frame you need to install the Zenhub extension in the browser (this extension is available for Google Chrome and Mozilla Firefox browsers). To install the extension, follow these steps:
- Enter in zenhub.com
- Click Add Zenhub to Github
- After that, go to the repository home page and you can see both the Boards and Burndown tabs, where you can see respectively the Kanban frame and the burndown for each sprint
The events provided by the SCRUM that will be used in the project:
- Sprint Planning: It happens every 2 weeks at the start of each sprint
- Retrospective and Review: It happens at the end of every sprint
- Scrum master: Responsible for ensuring that scrum values are adhered to and practices, practices and rules, as well as verifying that the style sheet and programming techniques are being properly scanned.
- Product Owner: Only person responsible for the management of the Product Backlog and for guaranteeing the value of the work performed, is the client that is part of the team.
- Team: Turn Product Backlog into increments of potentially deliverable functionality in each Sprint
The team consists of 9 members, soon we will have pairs between 8 members and one of them will be responsible for the role of scrum master, the pairing will be done by lottery among the members.
- Point: Classification of each user story, according to its complexity of implementation
- Velocity: The average points per iteration that a complete group
- Backlog: Is the name of the collection of stories that have not yet been completed in this iteration
- Burndown: Measures the progress of the sprint and gives indications of the team's work process
- Find areas of code that have not been exercised by the tests and perform them
- Code coverage analysis is a structural test technique
- Functional testing examines what the program performs without worrying about how it works internally.