BES
Playbook
Agile
Automated Testing
User Experience
Automated Application Modernization
Low-Code
Agile
Automated Testing
User Experience
Automated Application Modernization
Low-Code
1. Overview
1.1 Purpose
1.2 Audience
1.3 References
2. Agile Transformation
2.1 Waterfall Background
2.2 Introduction
3. Applying Agile Methods and Mindset Within The Air Force
3.0 Overview
3.1 Agile Contracting
3.2 Agile Stakeholder
3.3 Project Management
3.4 Agile CDRLs and Delivery
3.5 Status Reporting
4. Agile Architecture
4.1 Agile Management Tools
5. Agile Framework
5.1 Part I - Establish the Product Backlog (PB) and Constraints
5.2 Part II - Establish the Methodology
5.3 Kanban
5.4 Extreme Programming
5.5 Part III - Establish the Team
6. Appendix A - Key Event Plays
6.1 Scrum
6.2 Kanban
6.3 Extreme Programming
7. Appendix B - Key Personal Plays
7.1 Agile Lead
7.2 Product Owner
7.3 Business Analyst
8. Appendix C - Key Links
8.1 Agile in General
8.2 Agile Tools
9. Appendix D - Agile Terminology
9.1 Agile Terminology
10. Appendix E - Glossary
10.1 Glossary
11. Appendix F - CRDLs
11.1 CDRLS
1. Plays
1.0 Overview
1.1 Understand how Low-Code can be applied to your project
1.2 Delight the User
1.3 Agile is the Only Way
1.4 Empower the User
1.5 Select a Leader and hold them Accountable
1.6 Use Experienced Teams
1.7 Plan to rebuild
1.8 Automate Everything
1.9 Consider Cloud Hosting
1.10 Don’t forget the Interfaces
1.11 Fast Track ATO
1.12 Use Data to Drive Decisions
2. Overview
2.1 Introduction
2.2 Problem Statement
2.3 Purpose
2.4 Scope
2.5 Audience
2.6 Benefits
3. Low-Code Application Development
3.1 What is Low-Code?
3.2 Low-Code vs. No-Code Frameworks
3.3 Low-Code Use Cases
3.4 Low-Code Benefits
3.5 Low-Code Limitations
4. Low-Code Project Guidance
4.0 Overview
4.1 BES Digital Strategy
4.2 Low-Code Software Development Lifecycle
4.3 Team Structure
4.4 Project Management Processes
4.5 Key Project Metrics – KPI’s
5. Low-Code Platform Tool Selection Guidance
5.0 Overview
5.1 How to conduct Low-Code Platform Tool Analysis
5.2 Current Market Leaders (Forrester, Gartner)
6. Appendix A – Air Force Low-Code Sample Applications
6.1 Air Force Contracting Information Technology (CON-IT)
7. Appendix B – Low-Code Platform Evaluation Criteria Template
7.1 Evaluation Template
8. Appendix C – Acronyms
8.1 Acronyms
9. Appendix D – References
9.1 References
10. Appendix E – Chapter 5 Key Contributors
10.1 Chapter 5 Low-Code Playbook Contributors
1. Overview
1.1 Purpose
1.2 Audience
1.3 Benefits of Automated Testing
2. Test Automation
2.1 What is Automation?
2.2 Automation in Software Lifecycle Methodologies
2.3 Benefits to AF
2.4 Avoiding Pitfalls
3. Roles in Test Automation
3.1 Acquisitions
3.2 Management Support
3.3 Technical Support
3.4 Domain Support
3.5 Automation Team Members
4. Scope of Test Automation
4.1 Tools Target Areas
4.2 Test Levels
4.3 Test Types
5. Developing A Test Automation Solution
5.1 Approaches to Test Automation
5.2 Overall Architectural Considerations
5.3 Evaluation and Selection of Test Tools
6. Migrating From Manual to Automated Testing
6.1 What Makes Sense to Automate
6.2 When Should Automation Occur
6.3 Criteria for Creating New Automated Tests
6.4 Criteria for Converting Manual Tests to Automation
6.5 Transitioning Staff to Automation
7. Test Automation Development Lifecycle
7.1 Phases in Automation Development
7.2 Similarities to Application Development
7.3 Similarities to Manual Testing
8. Effectiveness Measurements
8.1 Effectiveness Measurements
9. Reporting
9.1 Reporting
10. Looking Ahead
10.1 Building Momentum in Test Automation
10.2 Keeping Abreast of the Technology Landscape
10.3 Continuous Improvement Activities
10.4 Making the Process Repeatable
11. Appendix
11.1 Appendix A: Resources
11.2 Appendix B: Test Tools
1. Overview
1.1 Purpose
1.2 Audience
1.3 Benefits of UX
1.4 Levels of Design Maturity
2. User Experience
2.1 What is UX?
2.2 UX Disciplines & Project Roles
2.3 UX in Software Lifecycle Methodologies
3. UX Principles & Methodology
3.1 UX Principles
3.2 UX Methodology
3.3 subpages
3.3 Phase 1: Research & Discovery
3.4 subpages
3.4 Phase 2: Conceptual Design
3.5 subpages
3.5 Phase 3: Detailed Design
3.6 Phase 4: Support
4. Web Design Standards
4.1 Introduction
4.2 General Interface Guidelines
4.3 Grids & Breakpoints
4.4 Branding/Logo
4.5 Global Headers & Footers
4.6 Page Layouts
4.7 Typography
4.8 Color
4.9 Iconography
4.10 Imagery
4.11 Buttons & Controls
4.12 Key Mobile Standards
4.13 Accessibility
5. Component Library
5.1 Introduction
5.2 Global Navigation
5.3 Icons
5.4 Buttons & Labels
5.5 Content Modules
5.6 Alerts & Messaging
5.7 Forms & Controls
5.8 Visualizations
5.9 Key Mobile Components
6. Appendix
6.1 Additional Resources
6.2 Alpha Standard Layouts
1. Overview
1. Overview
1. Overview
1. Overview
1. Plays
1.1 Application's Future Lifespan
1.2 Technical Baseline
1.3 Modernization Options
1.4 Target Application Solution
1.5 Modernization and Migration Plan
1.6 Executing the Plan
2. Overview
2.1 Introduction
2.2 Problem Statement
2.3 Purpose
2.4 Scope
2.5 Audience
2.6 Benefits
3. Automated Application Modernization
3.0 Overview
3.1 Guidance
3.2 Standards
3.3 Common Use Case
3.4 Approaches
3.5 Methodologies
3.6 Patterns
3.7 Barriers and Challenges
3.8 Recommendations
3.9 Lessons
3.10 Limitations
4. Modernization Tools
4.1 Tool Types
4.2 Tool Matrix
5. Lifecycle Processes
5.0 Overview
5.1 Agreement Processes
5.2 Organizational Project-enabling Processes
5.3 Technical Management processes
5.4 Technical Processes
5.5 Process Application
5.6 Application of Life Cycle Processes to Agile Evolutionary and Iterative Life Cycle Models
6. Project Guidance
6.0 Overview
6.1 Project Team
6.2 Key Personnel
6.3 AAM Project Phases and Work Items
6.4 Risk Identification and Mitigation Strategy
7. Determining the Best Modernization Solution
7.0 Overview
7.1 Identifying Viable Solutions
7.2 Analysis of Alternatives (AoA) Guidance
8. Solution Design and Implementation
8.0 Overview
8.1 Project Planning and Discovery
8.2 Design Principles
8.3 Design
8.4 Implementation
9. Measurement and Metrics
9.0 Overview
10. Appendix
10.1 Appendix A: Sample Design 1
10.2 Appendix B: Sample Design 2
11. Appendix C: Checklists and Templates
11.1 Checklist for successful application modernization
11.2 Legacy System Application Portfolio Assessment Framework
11.3 SANS Security Roadmap
11.4 BPD Tailoring Worksheet
1.1
Purpose
Agile Playbook Benefits
Consistent use of BEST practices and templates
Establishes AF Agile Body of Knowledge - continually improved by AF community
Provides "Quick Start" for new programs adopting agile working within AF
Provides non-technical professionals with an understanding of how to use agile
Builds confidence and effective communications across Government-Industry team
Identifies and reduces or eliminates barriers
Transforms culture from one focused on traditional processes to one focused on timely customer capability delivery.
feedback
Previous
Next