Uploaded image for project: 'SAFe Solution'
  1. SAFe Solution
  2. SS-8

Technical Debt - Feature Set

    XporterXMLWordPrintable

Details

    • Epic
    • Could have
    • PI3, PI4, PI7, PI9, PI10
    • None
    • Technical Debt
    • Data Processing, Obs Mgt & Controls, Services

    Description

      DEPRECATED EPIC!!! Please refer to this article for guidance in terms of technical debt: https://confluence.skatelescope.org/display/SE/Technical+Debt+Guidance

      We now flag technical debt on the Feature, Enabler, Story, Spike etc with a dedicated flag, and link the technical debit issue to the original Epic that is pertains to. 

       

       

      Technical debt accrues after managers/teams make hard decisions about time and resources. We don’t have unlimited resources, and we don’t have unlimited time.

      Refactoring addresses technical debt after the project has already been designed and started. 

      Ref: Solution Intent Defintion Document: https://docs.google.com/document/d/1ADF1xWYQ2j0vGfU-LmjrZcwRw8FmETHhWiNp89syOZ8/edit

      The definition of refactoring is to make changes to the structure of the design in order to improve a set of non functional or quality factors. Although it is a very common practice in coding, the underlying principles are equally valid in higher level architectural work. However, since it involves structural changes, refactoring can lead to significant amounts of work.  Thus refactoring is something that needs to be done continuously.

      Refactoring is also an alternative to trying to come up with the “perfect” structure upfront. Often the common patterns, base classes, categories and relationships are only determined once a set of entities exist that exposes these commonalities. For this reason optimising of the system needs to be done as the design proceeds rather than aiming upfront to achieve that goal.

      Attachments

        Issue Links

          Parent Of

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1154 Review and refactor developer portal layout for improved usability

          • Not Assigned - Priority is not assigned yet.
          • Funnel

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-586 Refactor Taranta to improve performance

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1513 Refactoring of CSP.LMC - part 2 - Subarrays and ObsDevices

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1514 Refactoring of CSP.LMC - part 3 - Master/Control Refactoring

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1665 usability fixes #2 - Taranta

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1689 Detect and address MVP vulnerabilities - Stage 3 (Clones SP-1488)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1868 usability fixes #3 - Taranta

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-554 Resolve technical debt in TMC code of MVP

          • Not Assigned - Priority is not assigned yet.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1153 Refactor 'sdp-prototype' into multiple repositories

          • Not Assigned - Priority is not assigned yet.
          • Done

          Spike - A time limited investigation to get some knowledge SP-1237 Review and define steps needed to onboard PSS repos at T0

          • Not Assigned - Priority is not assigned yet.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1247 Cheetah Pipeline Improvements related to OpenCL FPGA integration

          • Not Assigned - Priority is not assigned yet.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-465 Testing of Tango alarm handling

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Discarded

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1687 Refactor Test Cases for TMC code refactoring

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Discarded

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1608 Reduce Container Drag: Group TMC subarray nodes with subarray leaf nodes into a single device server

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1246 Refactor PSS PANDA Pipeline Code for improved stability and interoperability between CPU and GPU accelerators

          • Not Assigned - Priority is not assigned yet.
          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                m.bartolini Bartolini, Marco
                r.brederode Brederode, Ray
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Structure Helper Panel