-
Planning and Strategy
-
Requirements
-
- Customer Feedback Report
- Capacity Planning Report
- Stakeholder Input Record Example
- List of Customer Journeys
- Reverse Engineering: Legacy Inventory Management System
- Task Analysis: Customer Support Ticketing System
- Requirements Workshop: Employee Onboarding System
- Mind Mapping Session: Mobile Travel Planning App
- SWOT Analysis: New Food Delivery App
- Storyboarding Session: Mobile Health & Fitness App
- User Story Mapping Session: Online Grocery Shopping Platform
- Focus Group: Requirements Gathering for Fitness Tracking App
- Prototyping Session Example: E-Commerce Website
- Document Analysis Example: Hospital Management System Requirements
- Observation Session: Warehouse Operations
- Survey: E-Learning Platform Requirements
- Workshop Session Example: Requirements Gathering for Mobile Banking App
- Interview Session Example: Requirements Gathering for CRM System
- Event Storming Session: Retail Order Management System
- Generate Requirements from Meeting Transcripts
- Requirements Definition Process Example
- ISO/IEC/IEEE 29148 Systems and Software Requirements Specification (SRS) Example Template
- Show all articles ( 7 ) Collapse Articles
-
- Customer Requirement Document (CRD)
- Customer Journey Map
- Internal Stakeholder Requirement Document (ISRD)
- Internal System Use Case Example: CI/CD System
- User Stories & Acceptance Criteria
- Technical Specification Document Example
- BDD Scenarios Example for User Login
- Non-Functional Requirements Example
- Functional Requirements Specification Example
- Use Case Example: User Login
-
-
Communication
-
Design
- Functional Specification for Inventory Management Workload
- Technical Specification for Inventory Management System
-
- Overview of Design Diagrams
- High-Level System Diagram Standards
- User-Flow Diagram Standards
- System Flow Diagram Standards
- Data-Flow Diagram (DFD) Standards
- Sequence Diagram Standards
- State Diagram Standards
- Flowchart Standards
- Component Diagram Standards
- Network Diagram Standards
- Deployment Diagram Standards
- Entity-Relationship Diagram (ERD) Standards
- Block Diagram Standards
-
Operations
-
-
- Creating a Visualization Dashboard Guide
- Business Outcome Metrics Dashboard Guide
- Trace Analysis Dashboard
- Dependency Health Dashboard
- Guidelines for Creating a Telemetry Dashboard
- Guidelines for Creating a User Behavior Dashboard
- Improvement Tracking Dashboard
- Customer Status Page Overview
- Executive Summary Dashboard Overview
- Operations KPI Dashboard Example
- Stakeholder-Specific Dashboard Example
- Business Metrics Dashboard Example
- System Health Dashboard Example
- Guide for Creating a Dependency Map
-
-
-
- Event Management Policy Example
- Incident Management Policy
- Problem Management Policy
- Example Training Materials for Escalation
- Runbook Example: Incident Management with Escalation Paths
- Escalation Path Document Example
- Incident Report Example: Failed Deployment Investigation
- Incident Playbook Example: Investigating Failed Deployments
- Contingency Plan for Service Disruptions
-
-
-
Testing
-
Development
Sustainability Training Guide Example
ID: SUS_SUS2_5_sustainability-training-guide
Code: SUS2_5
Context
Optimizing resources provided to team members is crucial for minimizing environmental impact while meeting their operational needs. Tailoring resources to individual requirements helps reduce waste and maximize efficiency. This guide demonstrates how to align cloud resources with demand, creating a more sustainable work environment.
Key Considerations
- Right-Sizing Resources: Evaluate user workloads, selecting instances and configurations that match actual usage patterns, thus avoiding under- or over-provisioning.
- Auto Scaling: Implement auto scaling based on demand metrics to ensure elasticity, enabling resources to scale up or down as needed.
- On-Demand vs. Reserved Instances: Balance cost and sustainability by using on-demand instances for fluctuating workloads and reserved instances for stable workloads.
- Monitoring and Reporting: Continuously track resource utilization and overall consumption, adjusting configurations for optimal performance and minimal waste.
- Continuous Improvement: Regularly re-assess workloads and resource usage, adopting emerging technologies or configurations that optimize sustainability.
Example Implementation Scenario
A small development team frequently tests new applications with varying usage spikes. By enabling auto scaling, resources dynamically expand and contract to match workload peaks and troughs. Through monitoring CPU and memory usage over time, they downsize instances where usage is consistently low. This approach prevents over-allocation, leading to cost savings and reduced environmental impact.
Additional Best Practices
- Consider serverless architectures for intermittent workloads to further minimize resource usage.
- Leverage managed services that automate scaling and reduce overhead.
- Regularly review resource reports to identify underutilized services or idle resources.