Posted 5 months ago. Visible to the public. Repeats.

Project management best practices: Project team responsibilities

In a project team for a bigger project people have several roles:

  • Developer: at makandra
  • Project lead: at makandra
  • Project manager (PM): at makandra, external, or with the customer. In a smaller project this person is also the project lead.
  • Product owner (PO): with the customer

Developer

  • Development
  • Take responsibility for their stories. This includes always gathering all necessary information from the project lead or the PM, communicate blockers, make sure stories are merged, deployed etc.
  • Tell the project lead, if you're going to be out of work.

Project lead

  • Organizes the development
  • Makes sure all developers have enough work. Sometimes assign specific stories.
  • Organize a daily stand-up
  • Have control over the story tracker
  • Prepare and clarify stories with the PM
  • Keep an overview over all deadlines and the budget.
  • Project lead is the primarily responsible for the successful completion of the project.

The project lead can delegate parts of the project to a developer, who then takes responsibility for that part and takes over part of the project leads job in that regard.

In bigger teams, the project lead should try to assign topics to developers in such a way to avoid that unnecessarily many people have to be familiar with a specific topic.

Project manager

  • Not responsible for any technical aspects of the project
  • Requirement engineering with the customer
  • Create stories with the project lead
  • Communicate with the customer, including tunneling questions of developers (or have them talk to the customer directly, if required)
  • Timely acceptance of stories, if necessary together with the product owner.

If we have a dedicated internal PM, we should still treat them like an external PM. They are responsible for all PM work, but not primarily responsible for budgets, dead lines etc. This responsibility always lies with the project lead.

Product Owner

  • Clarification of requirements with the PM
  • Acceptance of stories with the PM (if necessary)
Growing Rails Applications in Practice
Check out our new e-book:
Learn to structure large Ruby on Rails codebases with the tools you already know and love.

Owner of this card:

Avatar
Tobias Kraze
Last edit:
4 months ago
by Henning Koch
About this deck:
We are makandra and do test-driven, agile Ruby on Rails software development.
License for source code
Posted by Tobias Kraze to makandra dev
This website uses cookies to improve usability and analyze traffic.
Accept or learn more