search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
SHAPING ARMY ACQUISITION


will evolve through iterative testing with users, often referred to as developmental operations (DevOps). See Figure 1, Page 26.


Create multidisciplinary, user-focused, collaborative teams.


Assembling multidisciplinary, collaborative teams whose members—developers, designers, engineers, domain subject matter experts, logistics, training, safety, cyber and testers— attend at least one Soldier touch-point event enables each team member to approach design and development with the user’s context in mind. Most developers have never met a user and have no concept of the environments in which they work. Te insights and empathy gained through immersion in a user’s expe- rience will create a common bond within the team and inspire all to stay focused on users and their needs even under the crunch of rapid development cycles.


Ensure development of a user interface style guide for use by all agile teams.


A style guide contains a set of design guidelines that specifies visual presentation of content, interactive elements and how they behave (buttons, form fields, dialog boxes, menus, navigation, etc.). See Figure 2, Page 27.


Ideally, a style guide should include reusable code snippets for front-end design elements to increase adoption by separate small Agile teams and should be in place before the start of coding. Adhering to the guide will ensure a consistent look and feel across feature sets, enabling users to transfer knowledge gained from using one feature set to another. Users can focus on performing a task rather than having to learn how the system works every time they use another one of its features. During internal vendor test- ing, screen layouts and interactive elements should be compared against the style guide to ensure compliance. Doing so will reduce the backlog created by identification of design inconsistencies during usability testing.


Refine the design with user feedback early and often.


Te Soldier-centered design team needs to work one step ahead of a sprint to collect user feedback, document the design and


SOLDIER-CENTERED FROM THE START


Soldier-centered design is so tightly woven into the fabric of the Precision Fires Dismounted program office that, when it came time to request authorization from the milestone-decision authority to proceed with limited deployment, it seemed only natural to invite Soldiers to the meeting. Forward observers from 1-320th Field Artillery Regiment, 2nd Brigade Combat Team, 101st Airborne Division (Air Assault) had participated in user juries and usability testing. The Program Executive Offi- cer for Command, Control and Communications-Tactical Brig. Gen. Robert M. Collins, asked them to weigh-in on the go or no-go decision.


They explained that, because the program office and developers listened to them and implemented the changes they requested, the system was much improved and they were looking forward to using it—“the earlier the better.” One Soldier claimed that, “it is 20 times better than the original PF-D.” Whether it is 20 times better is difficult to measure, however, usability test results have demonstrated a 40 percent increase in the ability of Soldiers to accomplish critical tasks on the first attempt—a measure of the intuitive- ness of the user interface.


A 29-point increase in its mean score on the indus- try-standard System Usability Scale brought the modernized system’s score 20 points above what is considered average and within the top 10 percent of scores for all commercial products tested. Products with scores this high are more likely to be recom- mended to a friend. Anecdotal evidence provided by one Soldier supporting this assertion was provided by one usability test participant who explained, “I was talking with some of the Special Ops JTACs [Joint Termi- nal Attack Controllers] I work with about this, and they thought it would be really cool to use because Call for Fire is something that we require them to do.” To expand on Kevin Costner’s famous line from “Field of Dreams,” If you build it right, they will come. The only way to build it right is to include Soldiers in the process.


Delivering real-world, operational capability enhancements relies on one fundamental principle: listening to users.


https://asc.ar my.mil 25


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