1 / 2

Open requirement management

This document outlines an effective approach to requirement management and governance through JIRA, facilitating the transition of requirements from internal to public JIRA. Each API will have one clear requirement, ensuring no confidential information is included. Requirements can be filtered by fix version to align with the roadmap. This includes tracking change requests for each API connected to the MeeGo.com backend status. New suggestions against API requirements are welcomed and will be evaluated for future releases, reinforcing a collaborative and transparent process.

keaton-hubbard
Télécharger la présentation

Open requirement management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Open requirement management • Open Governance • Moving Requirements from internal JIRA to public JIRA • One requirement per API • Contents, use cases, no confidential information • Can be filtered by fix version -> Roadmap • Change requests off API requirement • MeeGo.com backend status tracking • Change request against each API • This CRs belongs to MeeGo.com component as well • Tracking can be done at component level • Accept new suggestions against API requirements • They will be considered for future releases

  2. Public JIRA structure • http://bugreports.qt.nokia.com/

More Related