Do you know the non-Scrum roles of a project?

Medium to large software development projects have people on them with varying roles and responsibilities. In order not to double up, or miss something, it’s important to define what each should do.

Scrum already covers the roles of the Developers, the Product Owner, and the Scrum Master, but from a consultancy’s side, there’s also the Tech Lead and the Account Manager to consider.

Account Manager

• Communication from initial contact, to Initial Meeting, through to the Spec Review until the main body of work is booked
• Managing key relationships
• Getting T&Cs and any other required docs signed
• CRM data entry and maintenance of Company, Contact, Opportunities, and tracked emails
• Invoicing
• Conflict resolution
• Ongoing resourcing of the project and booking of Developers
• Budget discussions

Tech Lead

• Displays ownership of the project, and keeps the code quality high, and technical debt low
• Responsible for the delivery of the project into production
• Spec Review - Primary communicator with the Product Owner
• Project - Primary communicator with the Product Owner
• DevOps - Ensures good practices are followed e.g. release to production as frequenty as possible
• Responsible for the architecture and technical direction of the project
• Helps the Account Manager with technical areas of conflict management
• Keeps on top of the budget and timelines