Scrum Methodology
In Blue Infinity, We manage all our projects under Scrum methodology, working always with Project Manager certificates as Scrum Master.
Usually in one implementation/development project, our process is the next and we can guarantee support our customer during the complete lifecycle of the project in case that he is not used to working with this methodology.
1. We work together with IATA to create a list of User Stories, which are brief descriptions of things that users want do in the site, building the Product Backlog.
2. We will give each User Story an estimate, as a number of Story Points. Story Points are the currency of Agile, and correspond roughly to one hour of work.
3. IATA in prioritizing the User Stories, based on the value they add to the project and the amount of time we’ve estimated them to take. You’ll identify what order you’d like to see them completed in, and categorize them according to MoSCoW, which is our abbreviation for Must Have, Should Have, Could Have, and Won’t Have.
4. We estimate how many Story Points of work we can complete in a two week Iteration and select as many of the highest-priority User Stories as we can fit into an Iteration.
5. We implement the selected User Stories. This will often involve having discussions with you to make any decisions about interface or functionality.
6. At the end of two weeks, the selected User Stories will be 100% complete and tested. You’ll be able to use the site and verify that it works correctly.
We’ll repeat steps 4-7 as many times as necessary. You can re-prioritize User Stories if needed at any time.
For manage the projects under Scrum Methodology we use Jira and provide weekly reports to IATA with the status of the project.
Product Backlog Status (User stories management):
Sprint:
Sprint Report (weekly basis)
Usually in one implementation/development project, our process is the next and we can guarantee support our customer during the complete lifecycle of the project in case that he is not used to working with this methodology.
1. We work together with IATA to create a list of User Stories, which are brief descriptions of things that users want do in the site, building the Product Backlog.
2. We will give each User Story an estimate, as a number of Story Points. Story Points are the currency of Agile, and correspond roughly to one hour of work.
3. IATA in prioritizing the User Stories, based on the value they add to the project and the amount of time we’ve estimated them to take. You’ll identify what order you’d like to see them completed in, and categorize them according to MoSCoW, which is our abbreviation for Must Have, Should Have, Could Have, and Won’t Have.
4. We estimate how many Story Points of work we can complete in a two week Iteration and select as many of the highest-priority User Stories as we can fit into an Iteration.
5. We implement the selected User Stories. This will often involve having discussions with you to make any decisions about interface or functionality.
6. At the end of two weeks, the selected User Stories will be 100% complete and tested. You’ll be able to use the site and verify that it works correctly.
We’ll repeat steps 4-7 as many times as necessary. You can re-prioritize User Stories if needed at any time.
For manage the projects under Scrum Methodology we use Jira and provide weekly reports to IATA with the status of the project.
Product Backlog Status (User stories management):
Sprint:
Sprint Report (weekly basis)