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
ADAPTING EXPERIMENTATION AND TESTING


ATIS will replace 28 legacy systems and more than 70 applications with one authoritative system.


By capturing these insights, ATIS ensures that the features written for the program backlog are best informed from the very beginning of the process.


Te epic and feature refinement event takes place every week and brings together stakeholders from all of the program’s user communities. Tey collaboratively outline acceptance criteria, annotate traceability to functional requirements, identify possible interfaces and dependencies and further refine the scope of individual features. All these details are logged in GitLab, the program’s collaborative project manage- ment platform and version-controlled repository, during the live meeting to ensure that nothing is overlooked and that the process is open and transparent. While the development events may even- tually end as all requirements are initially framed into features, the refinement events will continue throughout the program life cycle.


ATIS’ iterative backlog refinement process fosters a culture of continuous improve- ment, maximizes collaboration and reasserts the Army training community’s steadfast commitment to delivering opti- mal value for Soldiers. It provides ATIS with opportunities to learn from past mistakes and incorporate lessons learned, honing its approach to crafting an ideal and relevant solution for the Army. Ulti- mately, the process provides teams with a well-informed starting point as they prepare to build and deliver features outlined in the program’s backlog.


BUILDING THE RIGHT TEAMS In September 2022, ATIS launched its first Agile Release Train (ART). Te ART is ATIS’ “team of teams,” consisting of cross- functional teams that collaborate to deliver the objective solution. Te ART plays a pivotal role in keeping the teams aligned to the same program vision, cadence of work and consistent iterative processes. It also manages cross-team dependencies and knowledge sharing, reducing risk and promoting efficiency. While the ART provides a powerful modular framework, offering the program a high degree of flex- ibility while ensuring an adequate level of predictability, the real work is done at the lowest level by the cross-functional teams.


Te teams on ATIS’ ART include both product teams and enabling teams. Te multidisciplinary product teams are build- ing the ATIS objective application, using a range of diverse perspectives and exper- tise to encourage innovation, effective communication and maximum agility in iteratively defining, building, testing and deploying software. Te enabling teams, on the other hand, define and convey the architectural vision, oversee DevOps alignment, lead system interface work, oversee seamless integration of the solu- tion and enable the work of the product teams in every aspect.


Te mix of responsibilities and relative autonomy of the teams require a diverse range of expertise. Although every posi- tion and role on each team is crucial for the success of ATIS, there are three


roles that ensure Soldiers have a voice in every facet of ATIS design and develop- ment: the government product owner, the user experience (UX) researcher and the UX designer. Tese roles provide the Army with three substantial reasons to be confident ATIS will deliver relevant and best value.


THE ROLE OF THE GOVERNMENT PRODUCT OWNER ATIS benefits tremendously from the decentralized team of teams approach prescribed by the Scaled Agile Framework, which provides teams with significant autonomy during their iterations, allowing them maximum flexibility in systemati- cally constructing ATIS one piece at a time. To optimize efficiency—while simultaneously ensuring collaboration, oversight and that user communities have a voice at the team level—ATIS has embedded government product owners on every team.


Tese team members act as the voice of the Army at the team level. Tey set the prior- ities for their teams at the beginning of each 10-week interval and receive demon- strations of the work being delivered at the end of each two-week sprint. At the end of each 10-week interval, they make the determination as to whether the delivered work realizes the business value planned.


ATIS has filled these crucial positions with government civilians and military person- nel from the Combined Arms Center and the Army Training and Doctrine Command. Tey’re the individuals most familiar with the capabilities of the legacy systems ATIS is subsuming and have the most holistic understanding of the require- ments. Teir embedded role on teams expedites decision-making by enabling them to provide on-the-spot feedback and guidance. Tis dynamic also provides the


https://asc.ar my.mil 93


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  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148