Recommendations to Succeed in Nexus Scrum Framework
Lessons Learned and Recommendations
This article will highlight important recommendations and Lessons Learned that I have experienced in the past during the application of Nexus Scrum Framework, to succeed in applying the Change.
Scrum Team:
Scrum Team (ST) consists of Product Owner (PO), Scrum Master (SM) and Development Team (DT) which are maximum 9 for a 4 weeks Sprint.
- Scrum team should follow the Scrum rules by book, it is being used everywhere else to make the process successful.
- Scrum team should commit to time frame rules, i.e. if the Sprint time span is over, the sprint should stop.
- ST may collaborate to resolve issues that could cause technical debts.
- Scrum team is one entity that is in whole responsible for the success or failure of a product. No game of blame…
Nexus Integration Team:
Nexus Integration Team (NT) is decomposed into Nexus Product Owner (PO), Nexus Scrum Master (SM) and Nexus Integration Team Members (IT)
The responsibility of the PO and SM are the same as the ones for a Scrum Product but they are on the Big Product Integration level.
Product Owner:
I have highlighted numerous times that a Product Owner (PO) must be able to understand business requirements and translate them into user stories. She/he will be responsible for the life-cycle of the Product (Backlog).
- PO is not a manager, she/he has no managerial power over people in the SCRUM…
- If PO is a department head, she/he should know that the Development team in the SCRUM is one entity even if they are from different departments.
- No PO can run more than 3 active Products concurrently unless she/he is Superwoman/man.
- PO should have emotional intelligence; an effort must be put in remaining polite whilst communicating with others.
- PO is responsible for the Product Backlog no one else should interfere with it.
- PO can’t change any story requirement once moved to a Sprint, she/he must consult the development team, they should decide.
- PO should know all details about development she/he can access the development team at anytime.
Scrum Master:
This is not a luxurious job, Scrum Master (SM) is a person who can facilitate Scrum team events, communications and development. SM should be able to remove any impediments that face the Product life-cycle.
- SM is not a PO, she/he is not responsible for the Product Backlog, she/he does not manage people and can’t add/edit/delete stories.
- SM could and should help the PO organize and write stories in the Product Backlog.
- SM does not get involved in business logic or operations unless was asked by the PO or development team.
- SM should make sure the SCRUM is running correctly, and that we are avoiding technical debts, by finishing of WIPs (work in progress). So he will make sure Scrum is being Scrummed.
- Again SM is not a department head, this is not a managerial position.
Development Team:
Development team (DT) members are cross functional and work autonomously and Independently, self managed to achieve Sprint goal.
- Department heads can be development team members.
- PO and SM can be part of the Development Team but this is not recommended.
- Development team members communicate and conduct daily stand-ups, for their communications there is no need for permissions from department heads or line managers, as this is a self managed environment.
- DT is one team, so there is no department, no game of blame, no “we and you”.
- DT should ask assistance from SM if they feel they are in need to assistance in operating the Scrum.
Nexus Integration Team Members:
Members of the Nexus Integration Team are normally members of the individual Scrum Teams in that Nexus. If this is the case, they must give priority to their work on the Nexus Integration Team; membership in the Nexus Integration Team takes precedence over individual Scrum Team membership. This preference helps ensure that the work to resolve issues affecting many teams has priority.
We have to avoid the 27 Sprint Anti-Patterns.
Good Luck…
