10 Suggestions for Architect of an Agile Team

Nice speech given by Tom Hollander from Microsoft Australia and he is making 10 suggesion for agile team architect to be sticked to. According to the tom, Agile team is employing number roles itself...

• PjM – is the Project Manager, similar to a Scrum Master, making sure the team is following the process.
• PdM – is the Product Manager, also known as the Customer or the Product Owner, determining what the product is supposed to be
• Architect – a solution/application architect
• Dev – the development team
• Test – the test team
• UX – the User Experience team
• Release – the Build and Release role taking care of the building process ( In our environment we used to called this role as Build Manager)

And the Suggestions are..

1. "Just Enough" Up front design
2. Start with a Vertical Slice - Mean start the development with a small module which cuts all the architectural and designs decisions made.
3. Just in time design each Iteration
4. trust your team.. be there for them
5. Write code
6. Be involved in everything related to the project
7. Drive a culture quality
8. Know when changes are required
9. Shield the team from external randomization
10. Write docs... but only is some to read them

Have a watch all video from MSTechEd or you can read speech summery from InfoQ

Regards

Lakmal