Project Methodology

We follow Scrum based Agile model for Project Management. This helps to promote development iterations throughout the life-cycle of a project. Each iteration passes through all levels of SDLC. At the end of every iteration, the team rechecks the project priorities.

Step 1: After requirement analysis, we list out all the client specifications in the Product Back log, which is an exhaustive list of requirements.

Step 2: Based on the nature of the project, we decide the sprint duration, i.e., 2 weeks or 4 weeks.

Step 3: A sprint planning meeting is held. In this meeting, each team member selects or the scrum master assigns a specific task, which he/she can complete in that sprint.

Step 4: The tasks selected by all members put together form a list called sprint back log.

Step 5: The requirements in that list are frozen till the end of the sprint, i.e., once the sprint planning meeting is over, the set of product backlog items remains unchanged throughout the end of the sprint.

Step 6: During the sprint, the developers work with the Product Owner to compose simple requirements. Developers prepare test cases before each code block and a code review is done to examine the code.

Step 7: The code is tested, reviewed, checked and finally installed on the designated file location for testing.

Step 8: A daily meeting is held during sprint. In that meeting, the members discuss about various issues they face during development and solutions.

During the meeting, each team member has to answer the following three questions:

• What have you done since yesterday?
• What are you planning to do by tomorrow?
• Do you have any problems preventing you from accomplishing your goal? (It is the role of the Scrum Master to remember these impediments.)

Step 9: At the end of the sprint, a Sprint Demo and Review Meeting is held. In this, a part of the product (the additions made during the sprint) is demonstrated to the client and other stake holders.

Step 10: The completed requirements are entered to another list called "Product burn-down chart". During this, the client can comment on the future requirements or requirement changes.

Step 11: These requirement changes are gathered and added to the product back log based on their priority.

Step 12: Selection of requirements for completion in a sprint is purely based on the priority.

Step 13: Finally, a sprint retrospective meeting is also done. This is a learning session. The team members can discuss about various issues they faced during the sprint, the methods they adopted to solve them, new things they learned etc.

Step 14: Then again, sprint planning meeting for the next sprint is carried out.

Feature and advantages
• Rapid and continuous delivery
• Handle late changes in requirements
• Intense cooperation between business people and developers
• Continuous improvement in technical quality and design
• Simple and Easy to implement
• Adaptation to changing environments