Following on from the discussion of the various flavours of Unified Process, there is some debate about the OpenUP process framework - is it Agile, or a reactionary result of the move to lighter processes?
The Rational Unified Process(RUP) was developed through the 1990's as a framework for software engineering best practices. Features such as iterations, simplicity, focus on value and regular feedback were identified as being important for Asuccessful software engineering. A number of authors have built methodologies that adapt UP to different project domains. This article examines some of them.
MomentumSI released yesterday its SOA Framework -Harmony. It contains 5 perspectives which include Lifecycle, Governance, Technology, Maturity Model and Information Model. A SOA Framework is typically used to structure the organization, processes, activities, metadata... deployed for service construction.
At Qcon London, Kevin Jones spoke from his experiences about Building Better Apps using MSF for Agile with Visual Studio Team System (VSTS). Using examples from Agile teams, he walked through the layers and components of Microsoft's tools, emphasising their flexibility. For Agile teams considering / already committed to Microsoft, this video provides an experienced viewpoint & may be worth a look.
The PM of the Eclipse Process Framework project explained in this presentation how IBM's Eclipse-based process tools allow teams to select the practices they want, to create a customised methodology that works for them. With a wiki and hooks to insert custom in-house documentation and practices, it provides a framework to configure the approach you want, or to grow into the approach you need.
Per Kroll is a director at Rational Software Corporation, where he's responsible for the development and management of the Rational Unified Process. In this interview, Per shares insights from his book 'Agility and Discipline', Agile practices for distributed development, how RUP is changing to support teams that want to customize it, and RUP vs. Agile.
When someone as well-versed with the processes people use to develop software as Ivar Jacobson says "Enough of Processes", one is bound to wonder why. Ivar Jacobson argues that the way we develop and share processes has to change.
Dave Thomas, founder of the team that produced the Eclipse IDE and the Visual Age Java IDE, recently evaluated Ivar Jacobson's new Essential Unified Process (EssUP). His article on Dr. Dobb's Journal called it "a dramatic improvement to UP," concluding that it "embraces agility."
It's always interesting to check out what's at the top of your colleagues' reading pile... This week, it's a selection from the reading list of InfoQ's architect and co-founder, Alexander Popescu. Alex thought so much of this book, he recommends it to all team participants.
Ivar Jacobson, one of the creators of the Unified Process, UML, and use cases, introduces his vision for a next generation development methodology that is both agile and comprehensive like the Unified Process (UP). His vision includes 'Intelligent Agents' which make customization recommendations based on tool usage patterns. Jacobson also talks about his views on UML, MDA, AOP, and the future.
A long and complex thread on the ScrumDevelopment list, set off by the phrase "Agile 2.0," has been exploring the past and future of Agile methodologies (for good or ill) including so-called "next generations" approaches like AUP, MSF Agile, and AMDD. Ron Jeffries, Ken Schwaber and Scott Ambler are just a few of the serious agilists who participated in this lively conversation.
Miko Matsumura interviews John Harby, an independent consultant, OASIS Techican Committee member and SOA practitioner on popular SOA implementation methodologies.
Ivar Jacobson, father of use cases and the Unified Process (UP) as well as one of the original "Three Amigos" of UML fame, describes his vision for a streamlined version of the UP which is published on a collection of cards instead of as HTML pages.
IBM announced today a host of new SOA tools which were launched at the Rational Software Development Conference 2006. These tools increasingly support governance through the lifecycle stages of design, development, deployment, testing and maintenance.
Software developers who firmly believe in an iterative approach must work for clients who, for various reasons, are rooted in a traditional methodology. This article discusses ways to help such organizations make a transition.