Cross functional teams
I was reading a book by Jeff Sutherland, who co-created Srum, and he mentions the old way of technology projects where:
1. Project requirements were documented
2. Passed to architecture team
3. Passed to implementation/development team
4. Passed to testing team
5. Passed to customer
My organisation is very much like this, there are no cross-functional teams, everyone operates in their silos!
How SHOULD this be organised? Each cross functional team should contain members of the architecture/development/QA team from requirements gathering to release?
To be cross-functional, a team must have all of the competencies and resources needed to create a release-ready product increment every Sprint. They should also be able to refine work so it is ready for Sprint Planning.
How those competencies and resources are distributed amongst team members is an implementation matter, but everyone should be able to collaborate effectively and with minimal waste.
One easy way is to take one person from each of those teams and form a Scrum Team with them. (maybe double or triple up on programmers)