Already a member? Log in

Sign up with your...

or

Sign Up with your email address

Add Tags

Duplicate Tags

Rename Tags

Share It With Others!

Save Link

Sign in

Sign Up with your email address

Sign up

By clicking the button, you agree to the Terms & Conditions.

Forgot Password?

Please enter your username below and press the send button.
A password reset link will be sent to you.

If you are unable to access the email address originally associated with your Delicious account, we recommend creating a new account.

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT

Links 1 through 10 of 19 by Jonathan Babcock tagged waterfall

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.

Share It With Others!

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.

Share It With Others!

Presentation on Agile.

Share It With Others!

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?"

Share It With Others!

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.

Share It With Others!

Like all other revolutions (this one being one of process from traditional SDLC to Agile/XP) - the new becomes the norm and the norm become bureaucratic - making further drastic changes required. I've always seen Agile and XP initiatives as an attempt to deliver greater value by removing the imposed management overhead and miss-steps (such as thinking mediocre can replace exceptional with the right process in place) - and, unfortunately now that many Agile/XP practices/processes have become the norm, they are now the anchor....just my opinion. Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Fitprojectguide.blogspot.com%2F2008%2F09%2Fxp-my-take.html

Share It With Others!

Overview

1. What's wrong with Waterfall? (for the zillionth time)
2. Iterative and Incremental Development
3. Variable Scope
4. Test First Programming

Share It With Others!

SCRUM software development process as compared to other delivery methodologies.

Share It With Others!

The main problem of the waterfall model is its inability to adapt. The waterfall project is split into separate stages and forces developers, project managers, and the end user to commitments to an outcome early on, even before the team knows how they wil

Share It With Others!

I assert that the value of agile methods has nothing to do with evolutionary requirements discovery, and everything to do with listening carefully to the customer and building a better understanding of their needs.

Share It With Others!

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT