We follow the combination of the agile and scrum methodology. We prefer this methodology as requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.
The key players in the methodology we follow
1. Product Owner: Our Business analyst team act as product owner in the process and are responsible for communicating the vision of the product to the development team. They also represent the customer’s interests through requirements and prioritization. The product owner has the most authority and is responsible for answering if the project goes away or fail. The product owner helps the team if they have any difficultly related to the project.
2. Scrum Master: Our technical team leader act as scrum master who is liaison between the business analyst and the team. The scrum master does not manage the team instead remove any impediments that are obstructing the team from achieving its sprint goals. The scrum master make the helps the team to remain creative and productive, while making sure that successes are visible to the product owner. The scrum master also works to advise the product owner about how to maximize ROI for the team.
3. Team Member: Our team is responsible for completing work. Our teams consist of six cross-functional members, plus or minus two individuals they include software engineer/developers, testers and UI designers. Each sprint, the team determines how they accomplish the work to be completed to meet the goals of the sprint.
SCRUM METHDOLOGY PROCESS FLOW
We follow the Pre-process before SCRUM methodology as shown in above figure.
Step 1: Presenting Project Proposal
Step 2: Requirement Gathering
Step 3: Defining the project scope and document it.
Step 4: Accepting project after client confirmation.
Once the project is in the house then process starts.
The process flow of methodology
1. Creating a backlog – Our product owner i.e. business analyst team and scrum team meet in order to discuss the priority and items on the product backlog. The BA team provides the vision for the product. The product backlog then prioritizes the list as per the requirement of project and ranks it according to importance.
2. Once the business analyst team creates the backlog, then there will be a Sprint Planning/Schedule Meeting. During the first phase of the meeting, the business analyst team describes to the team the goals of the project and explains the Product Backlog. During the second phase, the Scrum Team will select the items to be completed during the sprint from those with highest priority on the Product Backlog.
3. Once the items to be worked on have been selected, a potential Sprint schedule is constructed – taking into account the availability of the team members to devote their time to the project. The items in the Product Backlog are assigned and broken down into individual tasks. Once this occurs, this document is the Sprint Backlog.
4. The Sprint begins and lasts from 15-30 days. During the Sprint, no other tasks are added to the backlog. Daily Scrum begins when the sprint begins. The Daily Scrum is a 15 minute stand-up meeting where each member of the team gives a very brief report to everyone else – what they accomplished since the last Daily Scrum, what they hope to accomplish, and issues that have come up. Here, the Scrum Master will make note of issues and attempt to resolve them – after the meeting.
5. Product increment – As the daily scrum activity is regular for the particular sprint the product gradually increment with every day for the particular sprint schedule.
6. Sprint Review – once the Sprint ends, everyone gets together in a meeting to share what he or she accomplished during the sprint. The process begins again with a new list of prioritized tasks on the Product Backlog.
When all the schedule sprints are finished along with no new product backlog then the product is released.