Review: Roles in Software Development

Summary/review from this internal page

NRP:
1. PM (Product Manager):
  1. control and plan tasks
  2. in charge of holding meetings and taking care of meeting facilitation
  3. overseeing technical implementation
  4. managing documentation and maintenance
2. PO (Product Owner)
  1. understand the client’s specific needs
  2. to wear many hats
  3. being involved in project management
  4. crafting a compelling product roadmap
  5. maintaining a backlog
  6. acting as a liaison between the development team and stakeholders
  7. evaluating feedback
  8. Role demands:
    1. strategic thinking
    2. practical communication skills
    3. a deep understanding of business objectives and end-user needs
3. BA (Business Analyst):
  1. focus more on the technical aspects of the development process
  2. study and gather all information about the product
    - Requirement Gathering (?)
4. QA Engineer:
  1. often enter users’ shoes to identify whether the software works properly and meets quality standards
  2. to see weaknesses for improvement
  3. to supervise the testing process
  4. have coding skills
  5. compile a bug report:
    - describing all actions that led to this or that bug
PA:
1. PM (Product Manager):
  1. in charge of holding meetings and taking care of meeting facilitation
  2. overseeing technical implementation
2. EM (Engineering Manager):
  1. optimize the software development team structure when new developers join the team
  2. armed with a solid technical background
3. TL (Team Lead / Tech Lead)
SSC:
1. PO (Product Owner):
  1. are more into the profitability of the end product
2. BA (Business Analyst):
  1. act as a bonding agent between the market and engineers
  2. analyze users’ behavior/concerns
PL:
1. Software Developer

Others:

Consultant (Network & cloud expert)
Clients
End-users