How Teams work in Prakya
In many organizations, the product manager creates the features or user stories that are required for a portfolio epic. They are then assigned to a team and the teams are put to work. The teams are later monitored on their progress. In some cases, the teams can add user stories within a sprint, but have to take approvals beforehand.
This approach is taken either because managers are habituated to older models and feel that they have better control over the processes if they use those models, or because they are reluctant to adhere to the guidelines of transparency that Agile models advocate.
The above model defeats the very purpose of agility. Agile teams must have the skill to understand and prioritize value delivery from a customer point of view. They must be able to decide which stories to complete and have the freedom to create new stories when required.
Prakya believes that it’s the consciousness and awareness of the need that should drive and motivate the individual or a group of individuals at any level of hierarchy. As per SAFe, Agile teams are the first dimension of the competency and so it is for Prakya.
Apart from being self directed, focused and collaborative, Prakya’s teams map to the four fundamental topologies.
- They are organized around the workflow and deliver the value to the stakeholder directly.
- They are deeply skilled and possess expertise in specific domain
- They develop and provide platform as a service to the other teams
- They are adaptable to change and are capable of learning new technologies