- OveractDev White Box engagements are all and always Team engagements
- Team Members are never isolated, neither Heroes nor Villians, in front of our Client. We succeed and fail as a Team.
- Team members with daily collaboration must elevate issues to the Fulfillment Leader as needed.
- Tasks are implicitly assigned to the OveractDev team, not just to one individual.
- each team member relies on the rest of the team to complete the assigned tasks.
- the Team accepts responsibility for the completion of all tasks assigned to each member of the team
- Some Clients and some task management systems require us to assign a task to an individual. Our Clients are informed that, even though the task is assigned to a single team member, the responsibility for completion of that task (and all tasks) belongs to the entire team.
- Ultimately, the responsibility belongs to OveractDev. It is part of our brand, our reputation and our commitment that our work will be completed on time, it will work as specified, and it will have a minimum number of bugs.
- Team members assist each other with task completion for the following reasons:
- to cover for a team member that will be absent or is overloaded in some way.
- a complex aspect of the task goes to another team member’s expertise.
- a simple aspect can be completed by another team member, working under direction.
- to cross-train team members for team agility, transitions, increased bandwidth, etc.
- We consider the question of how we complete assigned tasks and, specifically, how we deploy our team resources to complete these assigned tasks to be an internal matter.
- This policy is NOT related to our transparency. The point of this policy is to make clear that we need to make these decisions on our own. That said, we are more than willing to discuss these decisions as they are made, or even as they are anticipated. Also, during the SCRUM it will be clear who is doing what.
- Note: SCRUM reports are made by the Team member to whom a task is ASSIGNED. If the Team member was assisted in some way (on a complex of simple aspect of the task), the member who assisted with the task usually does NOT need to report to the SCRUM.
- We support the process of having our clients interview Engineering/Technology Leads to determine our competency with certain technologies and/or tasks. For example, if we will be asked to develop an application using Flash, we will identify the team member who has this expertise and will be accountable for the completion of the Flash work. However, the Client understands that the Lead who is interviewed is the point of contact and the responsible person. This interview does not alter any policy outlined above.
