Comments on: Foundation Series: Software Process (Waterfall Process versus Incremental Process)

By: JoeyBurns

JoeyBurns — Fri, 31 Aug 2007 23:30:44 +0000

Wow, there is some really nice info here.
I’ll definitely come back soon to see everything.
Way to go! ;-)

Joey

By: RaymonWazerri

RaymonWazerri — Fri, 20 Apr 2007 23:01:52 +0000

Hey,
I love what you’e doing!
Don’t ever change and best of luck.

Raymon W.

By: Mac

Mac — Sun, 05 Nov 2006 05:27:12 +0000

incremental process in my mind, better bcoz ” Imagine software that can be delivered in two releases, where each release provides features that generate $10,000 per month in value.” And this thing is really cool!

By: A requirements documentation mistake --Tyner Blain

A requirements documentation mistake --Tyner Blain — Wed, 25 Jan 2006 13:01:48 +0000

[...] We were building and deploying this software with an incremental (not waterfall) deployment strategy – with anticipated quarterly rollouts. Once we got our arms around the amount of effort required to implement the first delivery, we had to adjust our schedule – the first deployment of anything was going to take six months. [...]

By: Tyner Blain » Where bugs come from

Tyner Blain » Where bugs come from — Sun, 22 Jan 2006 21:12:10 +0000

[...] Where bugs come from In the Foundation series post on software processes we introduce a definition of software process as three steps – (decide, develop, deliver). That post will provide some contextfor this discussion, which dives more deeply into the three steps (decide, develop, deliver). [...]

By: Tyner Blain » More on choosing the right software process

Tyner Blain » More on choosing the right software process — Mon, 09 Jan 2006 13:21:50 +0000

[...] He proposes that you pick your process (incremental, RUP, agile, waterfall) depending on the circumstances of each project. This builds nicely on the discussion we started in our Foundation series post, Software process (waterfall process versus incremental process). [...]

By: Tyner Blain » Stop wasting your time - don’t bother writing functional specs

Thu, 05 Jan 2006 04:01:19 +0000

[...] [Update: Waterfalls aren’t always bad. In this comparison of waterfall and incremental processes, we see when they can be good] [...]

By: Tyner Blain » Agile Requirements

Tyner Blain » Agile Requirements — Wed, 04 Jan 2006 07:35:00 +0000

[...] In the first of his articles, he talks about how the software-definition process should move from the general to the specific. Basically, the focus should narrow as time moves on, from an initial vision, to a set of features, to stories, and ultimately to specification. He makes the point that you should wait until the last “responsible moment” before each narrowing – not the last possible moment. The concept of a responsible moment was introduced by Mary and Tom Poppendieck in their book Lean Software Development: An Agile Toolkit for Software Development Managers. [...]

By: Tyner Blain » Welcome to Tyner Blain’s blog

Tyner Blain » Welcome to Tyner Blain’s blog — Wed, 04 Jan 2006 06:43:45 +0000

[...] I’ve set up this blog to keep track about thoughts I have in the software development space. I’m Scott Sehlhorst, president of Tyner Blain LLC. I wear a bunch of hats, playing different roles throughout the software development process. Tyner Blain was founded with two goals – helping customers and developing software. We pursue both consulting engagements and software development. We’re located in the surprisingly great city of Austin, TX (well, I was surprised when I got here), and we started operations on 05/05/05. I’m just now getting around to the blog. [...]