home

Agile Software Development and Business Analysis

By:  Scott W. Ambler

In this article Scott W. Ambler, Practice Leader Agile Development in the IBM methods group, overviews agile software development and the implications for business analysts.

AttachmentSize
Agile Software Development and Business Analysis.pdf39.51 KB

RUP not BRU

I'll let Scott answer your question to him.

I would however like to point out that RUP has NOT 'over-emphasized on "big requirements upfront" (BRU)as a requirements development approach' which would be very much a waterfall approach and anti-RUP.

RUP is a customizeable methodology and while it is possible to use a BRU waterfall approach as one a life-cycle model it is very much NOT recommended by RUP.

I have assisted several large organizations in the adoption of RUP and always professed an agile AUP approach with success.

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group