We offer two types of Agile engagement models - pooling-of-resources (or FTE) and time-and-material (or NTX) to serve our diverse clients - startups, ISVs, and enterprises. Our teams work in offshore, onshore, or nearshore configurations to mesh with your internal teams. Our delivery centers mimic the highest innovation standards of Silicon Valley thus providing greater outcome certainty. With thousands of sprints under our belt, our mature Agile-at-Scale Scrum development processes have been adopted by many of our clients. We are firm proponents of automation - from CI/CD pipelines, unit-testing, system-testing, and cloud-operations. Once we have the green light to start, we will utilize our Sprint-Zero to do a deep-dive on your requirements, distill them into user stories, work with you to prioritize them, define the macro architecture, and related activities for Agile delivery. We organize ourselves in feature-teams and support-teams. Feature teams are responsible for developing features. Support teams provide a common backbone to all the feature teams to meet sprintly objectives.
Zymr uses Sprint-Zero at the start of any project. The period of a week or two to align with clients’ to bootstrap the project. We align the engineering team on the project scope, define ontology, agree upon software tool stack, development processes, and other details. The end goals of Sprint-Zero are related to listing project milestones, we use a healthy backlog of user-stories, groomed Sprint-1, alignment of system architecture, tool stack, and processes.
Zymr recommends two-step scoring of effort estimates, macro, and micro for user-stories. Step-one is macro effort estimation by using the T-Shirt sizing of a backlog of user stories to get a hold on the project scope. Step-two is micro effort estimation by analyzing groomed stories for upcoming sprints. Using a Fibonacci sequence, effort estimates are refined from T-Shirt sizing to story-points, we ensure full-transparency and efficacy in the entire estimating process.
Zymr uses best practices to track agile development and delivery with ‘sprint velocity’ as a measure of team productivity. The velocity stabilizes after a few initial sprints, as our team builds the development muscles for efficiency. Some of the reasons for fluctuation in the velocity can be unmet dependencies, mid-sprint scope change, leaves, etc. To mitigate the development risks, we communicate contingencies early and conduct retrospective when the sprint ends.
Zymr ensures macro and micro delivery to seamlessly achieve the milestones. On a macro-delivery plane, each release/milestone/sprint has a theme decided by the Product Owner to communicate a cohesive vision for delivery. On a micro-delivery plane, each user-story has a ‘done-criteria’ that provides checklist including code-review, unit-testing, and functional testing, we produce a product-increment, and create a powerful demo at the end of every sprint.