<details><summary>Status</summary> <!--Status--> Marked by Epic Initiator: - [ ] Technical Lead Meeting (Date: DD.MM.YYYY) - [ ] Ready for Review Product Owner & Service Manager: - [ ] Ready for Steering Board Meeting Steering Board Meeting (Date: DD.MM.YYYY): - Vote result: (https://www.planitpoker.com/board/#/room/1e4ee16a6c644544aa75c9f9d3a4981c) - [ ] Ready for Backlog Analyzing & Prioritization: https://rwth-aachen.sciebo.de/s/fokQ8KEp2AKQuMy - [ ] Update Review (Back to Funnel) - [ ] Back to Open <!--Status#--> </details> --- #### Description: - An elevator pitch (value statement) that describes the epic in a clean and concise way. - For (customers) - Who (do something) - The (solution) - Is a (something – the how) - That (provides this value) - Unlike (competitor, current solution or non-existing solution) - Our solution (does something better – the why) - _Example: For the service manager who has to be informed about the users and status of Coscine the new KPI Generator is a tool to collect the necessary KPIs that shows the current numbers related to users and the system status. Unlike the current reporting our solution will be usable and more comprehensive for all related universities._ #### Key Stakeholders: - Names of Stakeholders, origin of epic marked bold (Mnemonic: People/Organizations who need to be inform when the epic is realized) - _Example: **IT Center Management** (SEPro Process), other participating universities_ <details><summary>Review</summary> #### Epic Initiator(s): - Source of the idea - _Example: Gitty Gitlab_ #### Business Outcome: - The measurable benefits that Coscine can anticipate if the epic is deployed. - _Example: The service manager always has the current and important numbers for the system. Other stakeholders can easily download the KPIs for their organization._ #### Acceptance Criteria: - What has to be there to close the epic at the end? - _Example: A KPI/System related number is collected by the KPI Generator in a database and can be downloaded._ #### Nonfunctional Requirements (NFRs): - NFRs define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs. Everything you have on your mind that could hinder the epic realization or that must be taken into account - _Example: Security: high – no personal information shall be collected (e.g. names or e-mail addresses) & a university shall have only accessibility to his/her own data. Reliability: medium – the numbers have to be collected at any defined time_ #### In Scope / Out of Scope: - Which kind of features / parts of the epic are to complex/time consuming etc? Which are possible to deploy? #### Epic Owner(s): - Responsible for Epic Analyzing & Progress - _Example: Conny Coscine_ </details> <details><summary>Votes & Prioritization</summary> #### Votes Each participant of the Steering Board vote based on the fist of five one of the following numbers for stage decisions (e.g. moving an epic from review to analyzing): 0. No way! This will not work. I'm not on board. 1. I see MAJOR issues that we need to resolve. 2. I see MINOR issues we need to resolve now. 3. I see minor issues we can resolve later. 4. I'm fine with this plan as it is. It's a good plan. 5. I love this! I will champion it. Best plan ever. For the backlog prioritization, the participants of the Steering Board agree per part of the prioritization formula (User-Business value + Time Criticality + Risk Reduction) on the following rating numbers: | Possible Rating Numbers: | 1 | 2 | 3 | 5 | 8 | 13 | 20 | |--------------------------|-----|---|-----|---|---|----|----| The management head of the steering board can choose to multiply the result with a strategic fit: | Strategic Fit | 0,8 | 1 | 1,5 | | | | | |--------------------------|-----|---|-----|---|---|----|----| The results are added to the open [excel sheet](https://rwth-aachen.sciebo.de/s/DkCEOAYeSSRcxQZ). #### User business value: - What makes the development necessary? Fore example, does it... Creates new customers? Satisfy existing customers? Is it more effective (reduce maintenance costs)? Is it an investment into the future? - _Example: The feature will increase the user satisfaction by allowing to individualize e-mail notifications_ #### Risk Reduction: - Is the tasks important to avoid or reduce technological or any other business risks? - _Example: New feature reduces risk of server time out_ #### Time Criticality: - Everything that should be considered in the prioritization in terms of urgency - _Example: Due to an update in XYZ in 6 months, the change must have been made by then_ </details>