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
SOLDIER-CENTERED AGILE


Not all feedback will result in innovation; however, if you are hearing consistently that something is problematic, it probably warrants further investigation.


applicable to both and extensible to non- Agile development efforts as well.


POINTS OF CONTENTION Agile is typically a developer-led philos- ophy whereas Soldier-centered design is driven by human factors practitioners, human-systems integration analysts or user experience professionals. Te Agile Scrum approach minimizes upfront plan- ning in favor of producing code quickly, whereas Soldier-centered design maxi- mizes upfront planning informed by user research (Soldier touch-point events) to produce a rough design that will evolve and crystallize through iterative user testing into a concrete final product. Agile measures progress by the amount of working software developed, while Soldier-centered design measures prog- ress by how well users can achieve their goals using the system.


Just like other government program


managers before us, we followed the Defense Acquisition Framework and integrated aspects of Agile development— sprints, releases, user stories, backlogs and burn down. We merged Agile devel- opment with Soldier-centered design to lay the foundation for system design— identifying the most frequent, critical and problematic tasks that require design


24


USERS FRONT AND CENTER


Through Soldier-centered design, end users are front and center in the development process. Rather than testing a prototype after design has been completed, this approach emphasizes early and frequent feedback from Soldiers throughout the process. (Image by Getty Images)


emphasis and documenting user stories by observing them at work in the field and sitting with them as they demonstrated system use during normal operations. We also conducted online surveys, focus groups and participatory design sessions. When software releases became available, we began conducting usability tests to identify design issues and enhancements, which is where the focus remains for both programs, at present. Along this journey, we found some things worked well and some did not. Here, we focus on what worked well and what we will do differ- ently in the future.


LESSONS LEARNED Te top 12 lessons learned during our efforts to integrate Soldier-centered


Army AL&T Magazine Spring 2021


design into Agile development include the following:


Build a strong design foundation with early Soldier-centered design activities.


Bringing human factors and human- systems integration onboard early to lead Soldier touch-point events builds a solid design foundation by validating user needs, documenting workflows, devel- oping user stories and identifying what is working well and what is not, as well as uncovering feature sets requiring design emphasis and capability gaps existing in manual processes and legacy systems. With these essential building blocks, the Soldier-centered design team will create a rough design of the user interface that


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