jonathan Babcock's Library tagged methodology →  View Popular

Prior to agile, many enterprises have followed a sequential, stage-gated, waterfall development model. In these cases, it’s likely that the Product Manager’s mindset has moved through a series of increasingly foreboding attitudes, as the figure below shows.

scalingsoftwareagility.wordpress.com/...re-agile-waterfall-development - Preview

agile waterfall methodology

For those of you who didn't attend Scott Ambler and Terry Quatrani's keynote "Software Development Strategies, Philosophies, and Techniques: Traditional vs. Agile" at this week's SD West conference, let me give you the gist of the first half:
Advocates of traditional software development approaches, such as waterfall and V-Model, are myopic bureaucrats who worship detailed specifications and denigrate the code necessary to build those specs.
Agile development practitioners, on the other hand, are logical pragmatists whose only goal is to build what the customer wants.
I sat in on Ambler and Quatrani's keynote to get a sense of whether cooler, more pragmatic heads had prevailed. I ended up more entertained than informed, and left with the impression that the debate remains as religious as ever.

blog.devx.com/...e-over-traditional-vs-agi.html - Preview

agile methodology

Talking last year with Scott Ambler who is IBM’s global lead for Agile development at the company’s Rational Software Conference, I made the mistake of suggesting that the methodologies and processes behind Agile almost form a kind of religion for developers who follow its creed.

community.zdnet.co.uk/...7,10012239o-2000458459b,00.htm - Preview

methodology agile religion

There are a lot of methods for developing software out there now. Choosing the best one for your company or team can be difficult - and that’s before you start adapting it to suit your particular situation. Here’s a brief history and overview of some of the more common ones you’ll come across. Each of them have good elements that you can make use of or learn from.

sheilapollard.wordpress.com/...hoosing-a-software-methodology - Preview

methodology lean agile scrum xp waterfall rup

Most interesting aspect of this is the comments. Lots of dialog questioning how well agile can work in less than ideal circumstances......

The Agile approach to managing software projects has been getting a lot of play recently. Why are people talking about it so much? Is this just the latest "new thing"? Or is there some real value to it?

"Agile," as a set of software development methods, was defined seven years ago, so the "flash in the pan" would have burned itself out long ago. The fact is that more and more organizations (from small shops to large corporations) are finding real value in Agility.

www.batimes.com/...108 - Preview

methodology agile requirements

There are some circumstances where an organisation's culture is possibly too different to successfully adopt agile. At the moment I can think of only 3 reasons why I wouldn't do agile software development:

1. If I was working for an organisation that believed it needed complete clarity about a solution before it could start a project. I believe this is a false positive, and it would be very hard to adopt agile in an environment where key stakeholders insist on this.

2. If I was working for an organisation where the relevant product owners couldn't - or wouldn't - commit to being actively involved throughout the project. I really do believe that active user involvement is the first principle of agile, and imperative for a project to succeed.

3. If I was working with a team that I didn't believe could cope with ambiguity, or didn't have sufficient communication skills to collaborate effectively with business colleagues or customers.

www.agile-software-development.com/...ns-why-i-wouldnt-do-agile.html - Preview

agile methodology

As you might know from previous posts, the Cranky Product Manager is pretty neutral on Agile / Scrum.

Yes, Agile is trendy. Everyone is doing it. Some consultancies out there have tied their entire brand to the Agile concept (digression - how smart is this when the inevitable backlash against something so over-hyped will inevitably occur?).

And don’t get the Cranky PM wrong, Agile/Scrum can help greatly with many types of product development problems. It’s good. It can be fun. But Agile/Scrum is not perfect. It has its problems too. Some of which have been elucidated more eloquently by others.

Well, the Cranky Product Manager is going out on a limb and declaring that:

The BIGGEST problem with Agile/Scrum is its crazy, insulting, demeaning, and threatening lunatic fringe.

crankypm.com/...agile-community-religious-war - Preview

agile methodology

Alistair Cockburn's treatise on why he prefers use cases over the user story and product backlog.

alistair.cockburn.us/Why+I+still+use+use+cases - Preview

usecase userstory scrum agile cockburn methodology

One of the bigger challenges facing software projects is determining when and how to begin the transition from specifying requirements to working on a system design. Questions arise during this phase, such as: "I'm on an Agile project--what design artifacts should I produce and when?"; "My project creates use cases; do I detail all the use cases first and then jump into design?"; and "Which requirements should I tackle first in design?"

www.stickyminds.com/sitewide.asp - Preview

requirements design methodology agile waterfall

Description of and commentary on results of a survey exploring the adoption rate of Test-Driven Development (TDD) and related techniques within the agile community.

www.ddj.com/212902568 - Preview

agile methodology

Presentation on Agile.

www.cooper.com/agile2008 - Preview

Agile waterfall methodology slides

Let’s be perfectly clear about one thing: 2009 will not only be known as the year the financial crisis hits in hard, it will also be known as the year everything turned agile. Please allow me to explain. The times when banks, insurance companies, car industries and the likes could start up multi-million software development projects of titanic ambition, with dozens of stakeholders, never ending requirements sessions and five year deployment plans are passed.

sanderhoogendoorn.org/blog - Preview

agile waterfall methodology

2.bp.blogspot.com/...f1.gif - Preview

SDLC methodology

The point is that SDLC management processes along with their human and non-human components form complex systems. Their selection and adaptation must be performed thoughtfully and nothing substitutes for experience here since to a large degree, human behavior will be the make or break factor.

drjbutler.wordpress.com - Preview

SDLC methodology agile process

Interesting article on when agile methods should be used. Includes an interesting graphic that illustrates, according to size, culture, criticalilty, personnel, and dynamism, whether agile or traditional methods make the best fit.

blogs.imeta.co.uk/...ds-on-my-software-project.aspx - Preview

agile methodology

Adapting scrum for a client that prefers RUP like delivery and terminology.

terborn.blogspot.com/...adapting-scrum.html - Preview

agile scrum methodology

OpenUP is a lean Unified Process that applies iterative and incremental approaches within a structured lifecycle. OpenUP embraces a pragmatic, agile philosophy that focuses on the collaborative nature of software development. It is a tools-agnostic, low-ceremony process that can be extended to address a broad variety of project types.

epf.eclipse.org/openup - Preview

methodology agile

In order to be “successful”, software has to meet a critical need that the user has. Good software solves a pressing problem. Great software does so in a way that seems natural to the users.

So what do I mean when I talk about software “failure”? Simply put, “failed” software is: software that doesn’t get used.

What are the consequences of failure? For internal software projects, it means wasted time and energy that could have been spent on things that the organization does need. For consulting houses, it means possibly not getting hired back by the client, or seeing your reputation diminished. For ISVs developing software/services to sell, it means lost revenue or even bankruptcy.

stuff.seans.com/...een-field-software-development - Preview

methodology project

Scrum depends heavily on commitment both at the small scale of an individual committing to a small piece of work, and at the large scale of an organization committing to real deep cultural change. Without that entire spectrum of commitment, it is unlikely that adopting Scrum will be anything but the latest fad imposed by management or done stealthily by staff.

www.agileadvice.com - Preview

SCRUM agile methodology

If you're spitting and fuming because you believe in software development processes, bear with me. I have a point to make, and you'll enjoy it.

If you've never believed in software development processes and you're cheering me on, take a seat and a deep breath. I have a point to make, and you're not gonna like it. But you need to hear it.

geekswithblogs.net/...process-is-a-lie.aspx - Preview

methodology sdlc