Skip to main content
Article thumbnail
Location of Repository

Crossroads News A Monthly Publication for Software and CM Professionals The Need for Agility in SCM

By Steve Berczuk and Steve Konieczka May


Summarizing from last month's article [1] Agility is “the ability to both create and respond to change in order to profit in a turbulent business environment…. What is new about agile methods is not the practices they use, but their recognition of people as the primary drivers of project success, coupled with an intense focus on effectiveness and maneuverability.”[2] Achieving agility while avoiding unproductive thrashing of the project requires high quality communication and tight feedback loops between competent team members and with project stakeholders. This allows the project team to iteratively grow the product architecture and functionality despite ever-changing customer requirements and priorities. Projects employing agile methods share the following key characteristics: • Adaptive – plans, designs, and processes are regularly tuned and adjusted to adapt to changing needs and requirements (as opposed to predictive methods that attempt to develop comprehensive and detailed plans/designs/requirements “up front”). • Goal-driven – focus on producing end-results (working functionality) in order of highest business value/priority [3]. “Agile approaches plan features, not tasks, as their first priority because features are what customers understand ” [4]. (as opposed to being document-driven or risk-driven) • Iterative – short development cycles, frequent releases, regular feedbac

Year: 2009
OAI identifier: oai:CiteSeerX.psu:
Provided by: CiteSeerX
Download PDF:
Sorry, we are unable to provide the full text but you may find it at the following location(s):
  • (external link)
  • (external link)
  • Suggested articles

    To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.