ISG Playbook
APIs...
- Adequate time for discovery, ability to market
- Users understand the changes and how it affects them
- What users can/should do differently to improve scores
- Better resources and data real-time to show users how scores are calculated
- What services are impacted? The cost impact for specific services and care types. (Need validation/clarification from Chris)
- A solution for counting/scoring of incomplete measures (Measure categories, required completion, incomplete submissions not accepted) is implemented so incomplete entries are not negatively impacting users
- ----------------------------------------------------------------------
- Better management of tech debt, reduction of security patches
- Clarity on work required to meet deadlines and policy implementation
- Delivery Predictability
- Reduced dependencies between teams to accelerate delivery
- Inclusion in roadmap discussions for enterprise tech changes
...
- Investigate testing practices to find opportunities to reduce patches/ tech debt
- Potential redistribution of devs to leads for other programs
- Impact analysis of work
- Value stream mapping/alignment (operational and development)
- Increase Practice discipline
- New jira project to align to LACE standards
- Work item hygiene
- Workflows
- Traceability
- Documentation
- Scrum across the board
- Implement/revisit/revise social contracts
- Value driven, non-implementation specific requirements
- Role responsibilities training (lace courses and “encouraged” attendance)
- Start doing the I&A workshop
- Revive the I&P iteration
- LACE Observation of refinement meetings (team & program)
- New jira project to align to LACE standards
...