InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Dave Thomas: EssUP Embraces Agility

Posted by Deborah Hartmann Preuss on Dec 28, 2006

Sections
Process & Practices,
Architecture & Design,
Enterprise Architecture
Topics
Modeling ,
Methodologies ,
Agile
Tags
UP ,
EUP ,
Process Adoption
Dave Thomas, managing director of Object Mentor and founding director of the Agile Alliance, recently took a look at Ivar Jacobson Consulting's (IJC) new Essential Unified Process.  His article on Dr. Dobb's Journal, The Essential Unified Process: New Life for the Unified Process revisits the evolution of Jacobson's ideas and evaluates this latest reformulation of the Unified Process.  He calls it  "a dramatic improvement to UP," concluding that it "embraces agility."

Thomas (not to be confused with "Prag
Dave" Thomas) is perhaps best known as the founder what became the IBM OTI Labs, responsible for initial development of the Eclipse open source IDE and the Visual Age Java development environment.  He has had plenty of time to create and reflect on the effectiveness of toolsets for software development.  Given his experience, it's interesting to read this in the article:
Despite the increased amount of process and tools, organizations soon observed that just increasing process didn't seem to result in more predictable, higher quality software. The Agile Alliance emerged from the Agile Manifesto when a community of successful software developers took a public position against the process/method heavy approach and instead focused on the practices that produce software and how one can improve them.
What distinguishes EssUP, in his opinion, is that it is simpler, more flexible and more extensible than previous expressions of UP.  He says "the approach is practice-centric instead of process-role centered."  In addition, it is presented with a lightweight and friendly approach which "makes learning the process easy, some might say even agile."

His review of the EssUP included these points:
  • Lean Set of Concepts: in the spirit of Lean Software, only those practices which one really needs.
  • Easy To Learn / Brief Presentation: a refreshing presentation approach using cards, and guidance sheets.
  • Embracing Agility: this is most apparent in the inclusion of a Team Essentials practice that focuses on social engineering and the people focussed side of agile development processes.
  • Open and Extensible: in contrast to the more comprehensive and self contained RUP, EssUP focuses on the essence and provides references to the original foundation works of software community,to make it clear that professionals have a body of knowledge which is essential to this work.
Rather than disparaging competing methodologies, the article ended on an optimistic note, saying "I see no reason why other non-UP processes, be they safety-critical or agile, could not be described using this same essential concepts and approach.."

  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

Call me EssUP by Paul Oldfield Posted
Re: Call me EssUP by Paul Oldfield Posted
  1. Back to top

    Call me EssUP

    by Paul Oldfield

    We've run short of TLAs, Ivar's new offering is known as EssUP for short, to distinguish it from Scott Ambler's Enterprise Unified Process - a prior claimant to the EUP TLA. Good to see Dave was using this accepted form in DDJ (that's Dr. Dobbs Journal, in case there are any other claimants...)

  2. Back to top

    Re: Call me EssUP

    by Paul Oldfield

    Thanks, Deb; that looks better now. Sorry for being picky.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.