Our work is based on Scrum, Kanban and Waterfall. Using these management frameworks helps us to follow estimates and develop high quality products. Waterfall approaches interest us the most of all, because we prefer to start new stage after finishing the previous one. It is also very conveniently for our clients, because this methodology need their requirements to be reviewed and approved, before the team can move to the next stage. The second structure, that we use, is Kanban. It is a visual framework that shows what to produce, when to produce it, and how much to produce. Applying both this methods in different situations helps to make our management really good.
Scrum – is an agile framework for an iterative software development. It is perfect for managing complex software and product development. We have chosen this methodology through it’s traditional, sequential approach. It consists of wide system with fixed-length iterations, called sprints lasting one to two weeks long. They allow our team to ship software on a regular cadence. At the end of each sprint, stakeholders and our team members meet to plan next steps. It helps us to get reviews from our clients constantly and eliminating many misunderstandings and confusion.
The benefits of Scrum include:
- More transparency and project visibility
- Increased team accountability
- Easy to accommodate changes
- Increased cost savings
Kanban is an Agile methodology. It approaches to process change for organizations which uses visualization with a kanban board, allowing a better understanding of work and workflow. It advises limiting work in progress, which reduces waste from multitasking and context switching, exposes operational problems and stimulates collaboration to improve the model.
The advantages of Kanban:
- Increases flexibility
- Reduces waste
- Easy to understand
- Improves delivery flow
- Minimizes cycle time
The waterfall model provides a structured approach. The model itself progresses linearly through discrete, easily understandable and explainable phases and thus is easy to understand. It also provides easily identifiable milestones in the development process. In common practice, waterfall methodologies result in a project schedule with 20–40% of the time invested for the first two phases, 30–40% of the time to coding, and the rest dedicated to testing and implementation. It helps to make really high quality products.
Why we have chosen Waterfall:
- Easy to use and manage
- Discipline is enforced
- Requires a well documented approach
Benefits of our approach
- We will embrace change under the objective of continuous improvement
- Breaking down the project into manageable units allows our team to focus on high-quality development and deliver it faster
- Customers have many opportunities to see the work being delivered, share their input, and have a real impact on the end product. They can gain a sense of ownership by working so closely with the project team.