SOLDIER-CENTERED AGILE
FIGURE 1 AGILE-SCD PROCESS INTEGRATION UNDERSTAND SCD-LED DESIGN FOUNDATION VISUALIZE
Lower fidelity mockups User feedback from testing
DESIGN/ REDESIGN
• Design feasibility • Developer questions
DEVELOPER-LED CAPABILITY
VENDOR TESTING
DELIVERABLES
• Human systems integration plan
• Design goals/emphasis • Validated requirements • Prioritized needs • User stories • Mission threads • Usability metrics
• System concept • Design elements • Feature flows • Style guide • Training plan • Documentation/job aids plan
• Mock ups/prototypes • Reusable design elements
• Sprint review feedback • User panel feedback
• Software release • Usability test results • Issue mitigation tracker • Style guide compliance • Configuration management • Logistics demonstration results
• Customer test results INTO AGILE DEVELOPMENT
The integrated design process reflects our lessons learned merging the two processes—identifying who best to lead specific design and development activities during each phase of the process as well as key deliverables that should influence or incorporate Soldier touch-point events.
FINAL PRODUCT
• Software • Training
• Documentation • Job aids
USER
ITERATE INNOVATE
DEVELOP TESTING
• Higher fidelity • Prototype code
EVALUATE
DELIVER
hand it off when development is ready to begin. Tey need to proactively test design assumptions and tackle designs ahead of the rest of the team. When using online surveys to gather quick feedback for alter- nate design implementations, users should perform representative tasks using the designs; grounding feedback in realis- tic scenarios will increase the validity of results. See Figure 3, Page 28.
Take time to plan when to conduct usabil- ity tests; sprints do not provide an obvious
point for inserting tests. Do not wait for perfect, clean code to reach out to users for feedback. Start early using paper prototypes, mockups, wireframes, simu- lations, stringing screens together in a slide presentation or even using emerging code. Neither the design nor the code needs to be complete to conduct part-task testing. Conduct smaller more frequent Soldier touch-point events.
Create user advisory panels.
Assemble a large user advisory panel and selectively invite members to provide feed- back during Soldier touch-point events on a regular or ad hoc basis.
Identify design goals and usability metrics.
Identify design goals and establish perfor- mance and preference measures and metrics upfront to drive design. For an intuitive design, consider a target such as 85 percent of target users, who have completed advanced individual training
26
Army AL&T Magazine
Spring 2021
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120
