iconiconiconiconiconiconiconiconiconiconlegacy_arrow-link-previouslegacy_arrow-linklegacy_closesocial_facebooksocial_googleplussocial_linkedinsocial_redditsocial_twittersocial_youtubeiconiconiconicon
03.18.2013

Becoming Agile—ASI Adopts AGILE Development Processes

Share:
Related topics: ASI
Six months ago, ASI fully adopted AGILE for both software and hardware teams as a way to make processes more efficient and deliver more value to customers. AGILE design processes focus on infusing quality and accountability into development tasks while also giving engineers more flexibility in dealing with unforeseen changes to their original plan.

Richard Netzley, Chief Operations Officer at ASI, recently gave a presentation to a group of masters and doctoral students at Utah State University's Instructional Technology and Learning Sciences department.

The students, who have been focusing on methods of design, invited Netzley to speak on the benefits ASI has seen from AGILE. The following blog describes ASI's AGILE installation and reactions to Richard's presentation.

While most AGILE companies follow a similar framework, the way each company employs AGILE is usually entirely unique to the company. "Each company will really need to take a little different approach and doing so will ensure that the system actually works," said Michael Doxey, ITLS Master's student who was present for the discussion.


ASI AGILE standup meeting
ASI's daily routine now involves AGILE standup meetings

The AGILE development process calls for breaking down large projects into smaller deliverable pieces developed over a short time frame.

The short development periods are called "sprints" or "iterations." With tangible examples at the end of each sprint, customers have an opportunity to provide feedback during the process rather than waiting until the final product is delivered. ASI currently uses two-week sprints with demonstrations concluding each sprint. ASI found that open communication and self-regulation are critical to AGILE. Software and hardware engineers gather for daily standup meetings which provide an open forum to set and discuss daily action plans. According to Netzley, each team member answers three questions: