May 16-20, 2011 | San Francisco Airport Marriott in Burlingame, California
Agile Adoption: Does it Have to be All In or Fold?
Rebecca Wirfs-Brock, President, Wirfs-Brock Associates
Adopting Agile approaches can have a huge impact on software development teams. Agile practices can help teams yield more accurate assessments of project progress, better ensure that what gets delivered will be useful, and lead to higher quality products that are more maintainable .
Yet it can be difficult to successfully transition to an Agile approach. Taking an all-or-nothing approach to adopting recognized Agile practices rarely succeeds. As a result, the pragmatic Agile change agent learns to adapt Agile practices to their organization’s unique context. This requires courage, convictions, and experimentation. Successful Agile adopters need to know when to push for changes to the “standard way we do things” and when to adapt or discard ill-fitting Agile practices. This talk will share lessons learned from experiences of those who’ve successfully adapted Agile practices presented by experience reporters that Rebecca shepherded at past Agile conferences. Not willing to leave it at that, Rebecca will conclude by challenging you to examine what it will take for you to succeed with Agile adoption.
Managing Architecture for Value
John Favaro, Associate Editor in Chief, IEEE Software
After years of research and industrial practice, the software architecture community has acquired a mature understanding of essential technological issues and is turning its attention to understanding the interaction of architecture with the business and strategy of the organization. However, understanding the value created by architecture is proving to be a difficult and elusive task. Agile approaches are making a positive contribution in this area, but managing architecture for value seems to require yet another mindset. This talk will explore the topic of architecture and value creation from several points of view, including a perspective of corporate strategy and finance.
Big Ball of Mud: Is This The Best That Agile Can Do?
Joseph Yoder, The Refactory, Inc.
While much attention had been focused on high-level software architectural patterns, what is, in effect, the de facto standard software architecture has seldom been discussed: the Big Ball of Mud. A Big Ball of Mud is a haphazardly structured, sprawling, sloppy, duct-tape-and-baling-wire, spaghetti-code jungle. We've all seen them. These systems show unmistakable signs of unregulated growth and repeated, expedient repair. Information is shared promiscuously among distant elements of the system, often to the point where nearly all the important information becomes global or duplicated. Somewhat to our astonishment, since our original statement, no one has ever undertaken to dispute this premise. Still, this approach endures and thrives. Why is this architecture so popular? Is it as bad as it seems, or might it serve as a way-station on the road to more enduring, elegant artifacts? What forces drive good programmers to build ugly systems? Can we avoid this? Should we? And how can we make such systems better?
May 16-20, 2011
SATURN 2011 Conference
News from SATURN
SATURN Network Blog Posts
Get the latest SATURN news, important dates, and announcements on our blog, signing up for our e-mail updates or following us on LinkedIn.
SEI Customer Relations
Phone: +1 412-268-5800
Toll Free (within the USA): +1 888-201-4479
FAX: +1 412-268-6257
Please tell us what you
think with this short
(< 5 minute) survey.