The Community for Technology Leaders
RSS Icon
Issue No.05 - Sept.-Oct. (2012 vol.29)
pp: 33-39
R. S. Sangwan , Pennsylvania State Univ., University Park, PA, USA
Lean practices use the principle of Little's law to improve the flow of value to the end user by eliminating sources of waste from a software development process. Little's law defines throughput as a ratio of work in process and cycle time. Increasing throughput (or productivity) requires continuously improving (that is, decreasing) cycle time while ensuring that the work-in-process limit doesn't exceed the capacity available to process the work. This article shares experiences regarding the role architecture plays in lean software management practices. Release plans that give as much emphasis to architecturally significant tasks as to feature-based high-priority functionality can achieve better outcomes by avoiding conditions that lead to wasted time and effort. The application of lean software development practices can improve with better practical guidance on how to manage architecture flow as well as feature flow.
Computer architecture, Product life cycle management, Programming, Productivity, Agile manufacturing, Software management, Software architecture, waste, software engineering management, lean software management, flow management, release planning, software architecture
R. L. Nord, I. Ozkaya, R. S. Sangwan, "Making Architecture Visible to Improve Flow Management in Lean Software Development", IEEE Software, vol.29, no. 5, pp. 33-39, Sept.-Oct. 2012, doi:10.1109/MS.2012.109
1. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, 3rd ed., Addison-Wesley, 2012.
2. W.W. Royce, “Managing the Development of Large Software Systems,” Proc. IEEE WESCON Conf., IEEE, 1970, pp. 328–338.
3. J. Coplien and G. Bj⊘rnvig, Lean Architecture: For Agile Software Development, Wiley, 2010.
4. K. Schwaber and M. Beedle, Agile Software Development with Scrum, Prentice Hall, 2002.
5. D. Leffingwell, Scaling Software Agility: Best Practices for Large Enterprises, Pearson Education, 2007.
6. J. Madison, “Agile Architecture Interactions,” IEEE Software, vol. 27, no. 2, 2010, pp. 41–48.
7. R. Sangwan et al., Global Software Development Handbook, Auerbach Publishers, 2006.
8. R. Sangwan et al., “Integrating Software Architecture-Centric Methods into Object-Oriented Analysis and Design,” J. Systems and Software, vol. 81, no. 5, 2008, pp. 727–746.
9. D. Reinertsen, The Principles of Product Development Flow, Celeritas Publishing, 2009.
10. N. Brown, R. Nord, and I. Ozkaya, “Enabling Agility through Architecture,” Crosstalk, Nov./Dec. 2010, pp. 12–17.
11. J.D.C. Little and S.C. Graves, “Little's Law,” Building Intuition: Insights From Basic Operations Management Models and Principles, D. Chhajed, and T.J. Lowe eds., Springer, 2008, pp. 81–100.
12. D. Anderson, Kanban: Successful Evolutionary Change for Your Technology Business, Blue Hole Press, 2010.
33 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool