TechWeb Special Reports

Beyond_Software_Agile_Oct13

Issue link: http://dc.tw.ubm-us.com/i/200697

Contents of this Issue

Navigation

Page 1 of 12

Beyond Software: A Agile for Product Development gile methods have proven effective for software development and have grown in popularity across a number of software disciplines, including application and enterprise software, as well as real-time and embedded software. Agile methods build capabilities using an iterative approach, as opposed to traditional approaches where detailed requirements are defined early and designs are completed in full before a single line of code is written. Agile incrementally defines requirements with priorities, partial component designs and working systems that evolve through iterations called sprints. The question remains, however: Do the 12 agile principles apply to more than just software? For example, can those principles be 2 UBM Tech applied to other products, such as physical components that contain both electronics and software engineering aspects, and possibly a mechanical engineering aspect as well? Agile principles are in line with (and in many ways borrowed from) lean management's approach, which includes building a factory floor feedback loop, breaking down manufacturing into smaller components, continually adjusting for bottlenecks, and changing processes based on customer feedback and inventory levels. Given that, it seems as though agile principles should directly apply beyond software development. However, the answer is not straightforward, because differences between software and physical components affect how agile is applied. Let's explore how agile can be applied in light of these differences. Agile's 12 Principles 1. Customer satisfaction 2. Changing requirements 3. A working, evolving product delivered frequently 4. Cooperation among all stakeholders 5. Individual motivation 6. Face-to-face conversation 7. The product as the principal measure of progress 8. A sustainable pace of work 9. Good design 10. Simplicity 11. Self-organizing teams 12. Adaptation to change October 2013

Articles in this issue

view archives of TechWeb Special Reports - Beyond_Software_Agile_Oct13