Yellow Sprint is the perfect scrum approach when you want to roll out IT projects quickly and flexibly in your organisation and in the supply chain. In short-cycle sub-projects called ‘sprints’, you achieve maximum results in record time. Yellowstar works with sprint themes, where every sprint has the same scale in terms of effort and costs, but the expertise in the sprint alternates for each theme. This produces greater functionality than the classic scrum method, so you get the most out of a progressive insight instead of being frightened off.
A small committed team with short lines and clear objectives keeps things moving. With Yellow Sprint, you can use your new insights in the next sub-project. That way, you keep the flexibility you need to adapt to changes and new insights. Yellow Sprint introduces a positive flow in your organisation and speeds up your processes so that you can grow further. This gives you clear project results so that you have a workable solution for the business. A company that uses Sprint also controls the project result and budget.
Yellow Sprint gives you speed, flexibility and growth
Ensures that you can continue to grow
Flexibility to anticipate changes
All roles are clearly distributed
By streamlining and optimising the organisation
Positive workflow results in flywheel effect
Space for progressive insight
What customers think about Yellow Sprint
How Yellow Sprint works
Frequently asked questions
How does Yellow Sprint work?
Yellow Sprint is the scrum working method where a large-scale IT project is split into smaller parts with budget and control moments. Every scrum project consists of at least three sprints that lead to a workable part-solution. Every sprint runs according to a fixed process and starts with a stand-up session at the scrum table. The scrum Master controls the project structure (the story), the definition of the objectives and the consensus (the Planning Poker sessions), the Sprint delivery sessions and the retrospective sessions with points for improvement. Scrum Ready sessions are the ideal preparation for Yellow Sprint and an agile supply chain.
Who is in the Yellow Sprint team?
A Yellow Sprint team consists of the members:
- Development team of Yellowstar
The development team consists of the Project Manager, consultants, developers and testers. They jointly help to define the project structure, the realisation, the tests, the checks, the estimate of the requisite effort and the definition of the technical specifications.
- Scrum Master
This person serves as a kind of orchestra conductor who organises scrum meetings and monitors the sprint progress.
- The Proxy Product Owner
The Proxy Product Owner is an intermediary from Yellowstar, who represents the customer if the customer has insufficient capacity and no time to describe the project or define the project structure.
- The Product Owner
The Product Owner is the client that describes the functions of the end product ,the IT solution, defines test scenarios and makes decisions about the budget, scope and planning.
The client will at least fill in the role of Product Owner (responsible for the budget) and appoint project board members.
Into which phases is a scrum project divided?
Yellowstar’s Scrum projects consist of three phases:
- The preparatory phase (sprint 0)
During the preparatory phase, the storyboard is drawn up, systems are set up and agreements are made to facilitate a smooth realisation phase (sprints).
- The realisation phase
The realisation phase (sprints) starts once sprint 0 has been accepted and is carried out by the entire team with a predefined cadence. The standard sprint duration is three weeks. Each sprint consists of the following components:
- Backlog Refinements: the technical solution and details are added to the stories to let the team know what activities have to be conducted
- Sprint Planning: a team session during which the stories to be tackled during the upcoming sprint are determined
- Realisation: the team works on the stories (development, technical testing, code review, functional testing, and release for external testing by the client)
- Sprint Delivery, the consultant provides a demo of the functionality delivered during the sprint
- Retrospective: the team evaluates the sprint and discusses positive aspects and points of improvement. The team defines action points that are incorporated into subsequent sprints.
- The end phase
Upon completion of the realisation phase, there is an end phase that can be used for a release to a production environment and to complete the project. During this phase, no new functionality is developed.
How are the tasks and responsibilities distributed?
Yellowstar is in charge of the project management, the delivery of the agreed scope, the planning and the future-proof architecture. The client/customer determines the definition of the scope, the prioritisation and the testing procedure. Then there are the two people who always play a central role: the scrum Master and the Project Owner. They are qualified and sufficiently skilled to quickly make choices and, together with the other parties, form a team that puts in a great team performance in close consultation.
What is the difference between the waterfall method and Yellow Sprint?
Yellow Sprint immediately puts new insights into practice and can quickly adapt to market changes. In the past, many IT projects were set up in line with the waterfall method. The requirements were defined in advance with no space for new insights during the development. These were long-term projects in which a short delay led to problems elsewhere in the project. When delivering the project, everything had to make way for a huge wave of changes that often met with resistance. At Yellow Sprint, the focus is being agile: working with manageable sub-projects in a committed team with clear roles, a common goal and a clear focus. Yellow Sprint supplies a workable result in a short time and on budget. The changes in the organisation are introduced gradually, and feedback from users is taken into account during the next phase. This generates support among users, who become accustomed to the process of continuous improvement using the agile software development technique. They also immediately experience the advantages and have the feeling that they can influence the process.