DZone
Agile Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Agile Zone > Key Roles in a Software Project

Key Roles in a Software Project

MVB Yegor Bugayenko identifies the roles and responsibilities of project team members at his company.

Yegor Bugayenko user avatar by
Yegor Bugayenko
·
Jul. 12, 16 · Agile Zone · Opinion
Like (3)
Save
Tweet
2.98K Views

Join the DZone community and get the full member experience.

Join For Free

I believe that several roles should be present in a majority of software projects. Managed by Teamed.io according to the principles of XDSD, we've got all of them in our projects. However, beware that in other management methodologies, these roles may have different meanings. This blog post is mostly for people who work with us, either as clients or freelancers.

There are just a few roles:

  • Project Manager (PM) is responsible for keeping the project under control. The PM reports to the head of our PMO.
  • Product Owner (PO) is a representative of the sponsor. The PO provides product requirements. The PO submits bugs and expresses any concerns or questions relating to them. Usually, the PO is a very technical person who knows how the product works and is capable of understanding the source code.
  • Software Architect (ARC) is responsible for the entire technical solution. The ARC is blamed for all technical problems. The ARC approves all pull requests before we can merge them. The ARC is the main point of contact in the project for the PO. The ARC makes all technical decisions. The ARC reports to the PM.
  • Developer (DEV) is a programmer and is responsible for closing bugs. The DEV reports to the PM.
  • Requirements Analyst (REQ) is responsible for the validation of the product. The REQ solicits requirements from the PO. The REQ demonstrates the product to the PO. The REQ submits new bugs when validation fails and the product needs changes. The REQ reports to the PM.
  • Quality Assurance (QA) oversees the correctness of our process. The QA approves each closed task before it's officially closed by the PM. The QA ensures that our process complies to our policy. The QA reports to the PM.

Besides all that, any role is encouraged to submit bugs when they find them.

Software architect Arc (programming language) Project manager pull requests Requirement Question answering dev Correctness (computer science)

Published at DZone with permission of Yegor Bugayenko. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Kubernetes Data Simplicity: Getting Started With K8ssandra
  • SRE: From Theory to Practice: What's Difficult About Incident Command?
  • How to Migrate to the Open-Source Cadence Workflow
  • IntelliJ Integration for Mockito

Comments

Agile Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo