- London: (+44) 20 3998 9611
- Email : hello@sovtech.co.uk
Your Rock Star Team
Our typical Agile Scrum Teams consist of 6-8 people including front and backend developers, UI/UX designers, QA Analysts, Product Owners, Business Analysts and Scrum Masters.
Product Owners,
Scrum Masters,
Developers
PO's determine what is being built and who it's being built for.
Scrum masters ensure project progression at the required velocity.
Developers build the product through high-quality, robust code.
UI/UX Designers,
QA Analysts,
Business Analysts
Designers create the beautiful designs and ensure excellent user experience.
QA's test the product to ensure it is fully functional and free of bugs.
BA's investigate and understand how the business works and aligns the product accordingly.
Two Week Sprint Process
Following sprint methodology, your Agile Scrum team works on a two-week sprint performing a number of ceremonies in order to optimise value and productivity.
Sprint Planning
Sprint planning is conducted at the start of each sprint. The sprint plan details the work to be delivered by each member of the Development Team. Sprints are set up in Jira and made visible to all team members and other interested stakeholders resulting in accountability. Tasks are further broken down into story points in order to provide a quantifiable weekly velocity report.
Daily Scrum
Daily Scrum meetings occur internally and provide an opportunity for each team member to provide an update to the rest of the team, discuss progress and report any blockers to velocity. Finally each member will let the team know what their deliverables for the day are.
Client Stand-Ups
A scrum meeting that involves all stakeholders and most importantly the client. The purpose of the client standup is to report project progress, communicate any issues faced, and receive business input where required.
Sprint Review
See the software progress at the end of each sprint during the Sprint Review. Clients are invited to participate and get a demo of the deliverables achieved within the sprint.
Sprint Retrospectives
Once the demo has occurred, the Sprint Retro is held in order to complete the two week sprint cycle. The purpose of the Sprint Retro is to discuss both positive and negative aspects of the sprint. This results in action learning and allows for continual team growth.