MITRE Defense Agile Acquisition Guide - Mar 2014multiple sprints Theme – A grouping of user stories or epics that may span multiple releases Teams often capture requirements in user stories and epics to provide a clear operational perspective of the tasks that define the lower level of detail to be completed. Epics are aggregations of user stories, often used to capture strategic intent. Epics may span multiple sprints and form a release, while user sprint. Some teams add a third level: themes, which group epics or user stories and span multiple releases. Teams capture and prioritize themes, epics, and user stories in databases known as backlogs, evolving0 码力 | 74 页 | 3.57 MB | 5 月前3
安全简介lengths - system continuous integration architectural runway Portfolio business epics architectural epics kanban epic system – limit WIP program portfolio management, enterprise architect0 码力 | 2 页 | 304.16 KB | 5 月前3
Open Discussion on Project Planningprogram must maintain a big picture, long-term view and focus on the next six-month release. DO epics and user stories to concisely define the desired system functions and provide the foundation for0 码力 | 2 页 | 49.30 KB | 5 月前3
Hyperledger Fabric 1.4.8 Documentationmeeting for consideration, feedback and acceptance. Release roadmap The Fabric release roadmap of epics is maintained in JIRA [https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104]. Communications0 码力 | 699 页 | 9.02 MB | 1 年前3
Hyperledger Fabric 1.4.9 Documentationconsidera- tion, feedback and acceptance. 12.3.6 Release roadmap The Fabric release roadmap of epics is maintained in JIRA. 12.3.7 Communications We use RocketChat for communication and Google Hangouts™0 码力 | 483 页 | 7.48 MB | 1 年前3
Hyperledger Fabric 1.4.9 Documentationmeeting for consideration, feedback and acceptance. Release roadmap The Fabric release roadmap of epics is maintained in JIRA [https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104]. Communications0 码力 | 701 页 | 9.02 MB | 1 年前3
Hyperledger Fabric 1.4 Documentationconsidera- tion, feedback and acceptance. 12.3.6 Release roadmap The Fabric release roadmap of epics is maintained in JIRA. 12.3.7 Communications We use RocketChat for communication and Google Hangouts™0 码力 | 483 页 | 7.48 MB | 1 年前3
Hyperledger Fabric 1.4.8 Documentationconsidera- tion, feedback and acceptance. 12.3.6 Release roadmap The Fabric release roadmap of epics is maintained in JIRA. 12.3.7 Communications We use RocketChat for communication and Google Hangouts™0 码力 | 483 页 | 7.48 MB | 1 年前3
Hyperledger Fabric 1.4 Documentationmeeting for consideration, feedback and acceptance. Release roadmap The Fabric release roadmap of epics is maintained in JIRA [https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104]. Communications0 码力 | 701 页 | 9.02 MB | 1 年前3
Hyperledger Fabric 1.4 Documentation
meeting for consideration, feedback and acceptance. Release roadmap The Fabric release roadmap of epics is maintained in JIRA [https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104]. Communications0 码力 | 678 页 | 10.02 MB | 1 年前3
共 23 条
- 1
- 2
- 3













