Targetprocess: Specify the Value Type of a Feature or Story

What are Value Types?

Value Types are used to categorize and group different types of work (both features and stories) in Targetprocess. These categories enable teams and Agile Release Trains to see useful reports such as how much effort is going into improving services versus maintaining services.

All features and stories should have a value type in Targetprocess.

Specifying the value type

1. Select the Story or Feature to open the details.
   • Stories and Features can be found in many views, such as Team Kanban or Team Backlog.
2. Expand the Info section on the right.
3. Choose the Value Type from the menu:
   • Business: Delivers direct value to the customer, such as enhancements that improve functionality.
     • Examples:
       • Enhancements requested by the business that improve functionality (new tables, fields, data areas)
       • PEAK: HR Benefits Life Events
       • CIA: Request Analysis - CDL data support for SAFE U (U Srvcs)
   • Enabler: Provides value through architecture, compliance, exploration and Infrastructure items that do not have direct value to the customer. Work items such as researching new technologies and fulfilling audit work which need to be completed for future value to be possible. Includes research Features and Spikes.
     • Examples: 
       • Current Data Platform Team work
       • Enterprise Data Admin related tasks
   • Technical Debt: Resolves inefficiencies that have been built into a system over time, such as refactoring, stabilization, and automation.
     • Examples:
       • Update access to a Peoplesoft page
       • Fixing the root cause of an issue rather than manually repairing it every time it fails, such as when a batch process periodically fails 
       • Consolidating scripts
       • Axway File Transfer Inventory Reconciliation and Review
       • Security - automatic logging and dashboarding
       • U of M report replacement
       • Decommissioning and cleaning up POC environments
   • Operations: Tracks routine and unplanned urgent work such as service requests, or incidents in a production environment, break/fix. 
   • Maintenance: Delivers planned work such as a system upgrade or routine patching.
     • Examples:
       • Snapshots
       • Environment refresh
       • Password rotation
       • HR Tax Update
       • Patches (Critical Patch Update)
       • CS Image
       • Non urgent, can be planned (bugs, etc)
       • Upgrades
   • Improvement: Improves team/ART efficiencies such as team processes or retrospective ideas.