Project Methodology
Our project management strictly adheres to Prince2 and scrum based methodologies as we cover all the levels of SDLC in SBL. This methodology places all our efforts in a bee-line order and augments our performance. SBL follows PRINCE 2 and Srum-based project methodologies for our swift and improved project flow.
PRINCE2
PRINCE2 is basically a project management method covering the organization, management and control of projects. The latest version of PRINCE2 was developed for incorporating the requirements of existing users and to augment the method towards a best-practice approach for the management of all sorts of projects. SBL's methodologies structure the project in a logical, organized way, using well-defined steps to prevent unexpected failures and huge overspends during projects.
SBL project methods help to bring together different groups of people involved, in the project together with the client, suppliers, and the user. Through PRINCE2, SBL provides a common language across all the involved groups.
These principles are
- A project is a finite process with a definite start and end
- Projects always need to be managed in order to be successful
The key features which SBL follows through Prince2 are:
- Giving focus on business justification
- Well-defined organization structure for our project management team
- SBL's product-based planning
- Our highlight on dividing the project into controllable and manageable stages
- Flexibility applied at different levels of project.
By the Prince2 project methodology, SBL's projects offer:
- A well-controlled and organized start, with a definite middle and end
- Regular progress reviews against plan and business case flexible decision points
- Regular management control of any deviations from the plan
- The timely involvement of management and stakeholders and place during the project
SCRUM
SBL also follows Scrum-based agile model for Project Management to promote development iterations throughout the life-cycle of a project as it is an agile, iterative, incremental process for developing a product. Each iteration passes through all SDLC levels. At the end of each iteration, the team rechecks the project priorities.
The SBL ways of Scrum-based method:
- Step 1: After an initial requirement analysis, all client specifications are listed out in the Product Back log.
- Step 2: Based on the nature of the project, we decide the sprint duration, i.e., 2 weeks or 4 weeks which can vary with each project.
- Step 3: A sprint planning meeting is held where each team member selects / the scrum master assigns a specific task to the team members.
- 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 where the members discuss about various issues they face during development and solutions.
- 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
- Step 9: At the end of the sprint, a Sprint Demo and Review Meeting is held where a part of the product (the additions made during the sprint) is demonstrated to the client and other stakeholders.
- 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 which 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: Again, sprint planning meeting for the next sprint is carried out.
Advantages SBL's Scrum based project methods
- 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