At TechMojo, we believe in autonomous agile POD teams of size 6 so that they are nimble and easily scalable. Usually, our POD team comes with a diverse skillset consisting of developers, and quality assurance engineers. Customers can engage with TechMojo in the following three different engagement models. Techmojo is very quick in ramping up its resources and their POD teams so that customers can scale their business at a rapid scale.
Engagement Model #1
In this model, the customer deploys the product owner and TechMojo deploys the POD team consisting of all required skills to deliver the product.
| TechMojo’s POD team is responsible for | The customer Product Owner is responsible for |
|---|---|
| Defining the process with due consulting and collaboration with the customer. | Authoring the epics, and user stories as per the Definition of Ready (DOR) by taking necessary support from the POD team during the grooming session |
| Agreeing on the sprint backlog by referring to the capacity available at hand | Prioritization of user stories for the respective release and sprint planning sessions. |
| Delivering the sprint backlog with quality as per the set Definition of Done (DOD) | Provide feedback during Product demo and biweekly governance meetings to POD teams |
| Providing the sprint Demo to the Product owner | |
| Come up with action items to adapt to the feedback received from the Product Owner | |
| Come up with action items to adapt to the feedback received from the Product Owner |
The POD team, the scrum master, and the product owner work in collaboration to the best of their capacity to resolve the impediments at hand.
As part of governance procedures, Techmojo’s srum master and customer Product owner will have a bi-weekly review of the progress made during the just concluded sprint. The POD team seeks feedback from the customer product owner and takes necessary adaptive steps. Similarly, Techmojo’s CXO team will have monthly reviews with the customer CXO team to review the progress made during the last reporting period and capture customer feedback. The TechMojo team comes up with clear action items so that the captured feedback is turned into positive change.
The advantage of this model is that the customer will have clear control over the prioritization of the user stories for the respective sprints or releases. TechMojo team owns the process and delivery of the agreed payload with due quality. TechMojo tries to enable customers to experience certainty in outcomes through their execution methodology’s predictability, transparency, and consistency.
Engagement Model #2
In this model, the customer deploys the product owner and thus owns the authoring of user stories and their prioritization for the sprints. The joint POD team consists of a few resources from TechMojo and a few resources from the other vendor. TechMojo provides a scrum master and owns the project management of project delivery so that the set scope is delivered within the set schedule along with the quality. The Vendor resource manager supports TechMojo’s scrum master in terms of ensuring vendor resources’ skill, availability, and collaboration.
| TechMojo's Responsibilities | Customer's Responsibilities | Vendor's Responsibilities |
|---|---|---|
| Defining the process with due consulting and collaboration with the customer. | Authoring the epics, and user stories as per the Definition of Ready (DOR) by taking necessary support from the POD team during the grooming session | Seek periodic feedback on their resource quality, capability, and collaboration and address them timely |
| Agreeing on the sprint backlog by referring to the Joint POD team’s capacity available and consent | Prioritization of user stories for the respective release and sprint planning sessions. | Work in collaboration with TechMojo scrum maser and customer product owner |
| Delivering the sprint backlog with quality as per the set Definition of Done (DOD) | Provide feedback during Product demos and biweekly governance meetings to POD teams | Ensure that Vendor resources stay motivated and does not change the team at least for one year from the date of their inception into the respective teams |
| Providing the sprint Demo to the Product owner | Resolve the concern raised on Vendor resource skill, skill capability, and collaboration | Come up with action items to adapt to the feedback received from the Product Owner |
| Conducts daily stand-up meetings and sprint retrospective events. | Raise concerns on the Vendor resource skills, skill capability, and collaboration |
The joint POD team, the scrum master, and the product owner work in collaboration to the best of their capacity to resolve the impediments at hand.
As part of governance procedures, Techmojo’s srum master and customer Product owner will have a bi-weekly review of the progress made during the just concluded sprint. The joint POD team seeks feedback from the customer product owner and takes necessary adaptive steps. Similarly, Techmojo’s CXO team will have monthly reviews with the customer CXO team to review the progress made during the last reporting period and capture customer feedback. The TechMojo team comes up with clear action items so that the captured feedback is turned into positive change. The vendor’s resource manager or their resources can be invited to any of these meetings depending on the need and context of the meetings.
The advantage of this model is that the customer will have clear control over the prioritization of the user stories for the respective sprints or releases. The customer still can employ different vendor resources for their special technical capability along with TechMojo’s technical resources. TechMojo team owns the process and delivery of the agreed payload with due quality. TechMojo tries to enable customers to experience certainty in outcomes through their execution methodology’s predictability, transparency, and consistency.
Engagement Model #3
In this model, the customer deploys the product owner, scrum master, and a few technical resources from their organization. TechMojo deploys a few resources from their organization. It is a complete staff augmentation model for TechMojo where overall project management responsibility and accountability of deliverables are taken up by the customer teams. TechMojo is responsible for ensuring their resources’ skill, availability, and collaboration.
As part of this, TechMojo’s account manager periodically seeks feedback from customer organizations about issues faced for TechMojo’s resources skill, capability, and collaboration. TechMojo’s account manager notes down the feedback along with clear examples and brings the needed change from their resources.
The advantage of this model is that the customer will have clear control over the prioritization and execution of the technical delivery. They can leverage TechMojo’s resources for their special technical capability. TechMojo tries to enable customers to experience certainty in outcomes through their execution methodology’s predictability, transparency, and consistency.