View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

PM-Dev-QA Interaction Process

Contents

PM should do:

  1. Write Functional Spec (FS) as a Draft.
  2. Get FS Draft to be reviewed by:
    1. The Customer (for example, HIS) in case of collaborative development
    2. The GPS team as a representative of the Customer for us
    3. Dev/QA in any case, and moreover in case of Internal projects
    4. UX* in case the feature involves an important GUI change
  3. Write FS Final taking into account all parties feedback
  4. Get FS Final signed-off by both Customer (if applicable) and/or GPS/Dev/QA/UX* teams
  5. Write user document and help on translation

Points to be noted:

Dev Team should do:

  1. Review FS Draft
  2. Sign-off FS Final
  3. Write Technical Specification Draft
  4. Prototype the feature to be implemented. In case of GUI-heavy features, UX needs to be consulted to design mockups of screens and flows before actual prototyping (code) starts.
  5. Present a prototype and Technical Specification Draft to the Product Owner, Customer (if applicable), GPS, UX* and internal development committee: OB Functional and Technical experts (EAR, GDA, PSA, those of them who can attend) and Management.
  6. Coding / Feature implementation
  7. Inform QA when they estimate code is going to be ready for testing
  8. Development feature testing in a wide set of environments: main-ora, main-pg, qsqss. For modules it also includes installation tests in these different environments from Stage
  9. Deliver feature (published in Stage for Modules, branch access for big core changes) to QA for testing
  10. Fix the bugs reported by QA
    1. After fixing the bugs Dev team has to execute all the test cases written by QA.
      1. If the project has lots of test cases (more than 10) then developers only test the critical or important ones. QA will guide Dev Team here.
    2. Dev team to send a confirmation to QA that all the tests passed before delivering feature back to QA for re-test
  11. Final feature presentation to the Product Owner, Customer (if applicable), GPS, UX* and internal development committee: OB Functional and Technical experts (EAR, GDA, PSA, those of them who can attend) and Management.
  12. Feature release/delivery (CR publication, PI merge)

Points to be noted:

QA Team should do:

  1. Read the functional specs.
  2. Sign-off the FS
  3. Design the test cases and setup environment required (Oracle and Postgre)
  4. Once code is ready, execute the test cases just once and log all the issues
  5. Once Dev team confirms to QA that the issues are fixed and tested QA does the final round:
    1. Second round of execution of the test plan
    2. Closing resolved issues
  6. Green lights for Release

Retrieved from "http://wiki.openbravo.com/wiki/PM-Dev-QA_Interaction_Process"

This page has been accessed 3,874 times. This page was last modified on 24 March 2010, at 18:17. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.