Comments on: The Case Against Window Dressing http://www.bp-3.com/blogs/2009/06/the-case-against-window-dressing/ A Blog about Enterprise BPM and Business Process Improvement by the folks at BP3 Sun, 12 Feb 2012 05:30:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Process for the Enterprise » Blog Archive » Breaking Down the Version 2 Barrier http://www.bp-3.com/blogs/2009/06/the-case-against-window-dressing/comment-page-1/#comment-239 Process for the Enterprise » Blog Archive » Breaking Down the Version 2 Barrier Tue, 14 Jul 2009 00:37:25 +0000 http://www.bp-3.com/blogs/?p=848#comment-239 [...] a recent post, the Case Against Window Dressing, I pointed out that a process can be deployed with nearly all the integrations scheduled for [...] [...] a recent post, the Case Against Window Dressing, I pointed out that a process can be deployed with nearly all the integrations scheduled for [...]

]]> By: Scott Francis http://www.bp-3.com/blogs/2009/06/the-case-against-window-dressing/comment-page-1/#comment-233 Scott Francis Fri, 03 Jul 2009 04:32:55 +0000 http://www.bp-3.com/blogs/?p=848#comment-233 Sandy - how right you are about the difficulties of breaking down the v1 / v2 barrier. There is a method to the madness of breaking down those preconceived notions, which are reinforced by the actions of both IT *and* Business. This might be fodder for a good post, but here are a few of the ideas: The first step, of course, is to fund for more than one version up front! The corollary to this is that if you only have budget for one version, break it up into two versions artificially. The second step is to show incremental releases that don't go to production. Get the business used to seeing interim progress, and get IT used to be accountable for providing progress throughout the duration of the project. The third step is to get the business involved in prioritizing what goes in and out of the next incremental release. The last step is to actually live up to your commitment to get started on v2 right away. Or even before v1 ships, if you really want to send the right messages... Sandy –

how right you are about the difficulties of breaking down the v1 / v2 barrier. There is a method to the madness of breaking down those preconceived notions, which are reinforced by the actions of both IT *and* Business.

This might be fodder for a good post, but here are a few of the ideas:
The first step, of course, is to fund for more than one version up front! The corollary to this is that if you only have budget for one version, break it up into two versions artificially.

The second step is to show incremental releases that don’t go to production. Get the business used to seeing interim progress, and get IT used to be accountable for providing progress throughout the duration of the project.

The third step is to get the business involved in prioritizing what goes in and out of the next incremental release.

The last step is to actually live up to your commitment to get started on v2 right away. Or even before v1 ships, if you really want to send the right messages…

]]> By: Scott Francis http://www.bp-3.com/blogs/2009/06/the-case-against-window-dressing/comment-page-1/#comment-4587 Scott Francis Fri, 03 Jul 2009 04:32:00 +0000 http://www.bp-3.com/blogs/?p=848#comment-4587 Sandy - how right you are about the difficulties of breaking down the v1 / v2 barrier. There is a method to the madness of breaking down those preconceived notions, which are reinforced by the actions of both IT *and* Business. This might be fodder for a good post, but here are a few of the ideas: The first step, of course, is to fund for more than one version up front! The corollary to this is that if you only have budget for one version, break it up into two versions artificially. The second step is to show incremental releases that don't go to production. Get the business used to seeing interim progress, and get IT used to be accountable for providing progress throughout the duration of the project. The third step is to get the business involved in prioritizing what goes in and out of the next incremental release. The last step is to actually live up to your commitment to get started on v2 right away. Or even before v1 ships, if you really want to send the right messages... Sandy –

how right you are about the difficulties of breaking down the v1 / v2 barrier. There is a method to the madness of breaking down those preconceived notions, which are reinforced by the actions of both IT *and* Business.

This might be fodder for a good post, but here are a few of the ideas:
The first step, of course, is to fund for more than one version up front! The corollary to this is that if you only have budget for one version, break it up into two versions artificially.

The second step is to show incremental releases that don’t go to production. Get the business used to seeing interim progress, and get IT used to be accountable for providing progress throughout the duration of the project.

The third step is to get the business involved in prioritizing what goes in and out of the next incremental release.

The last step is to actually live up to your commitment to get started on v2 right away. Or even before v1 ships, if you really want to send the right messages…

]]> By: Column 2 : links for 2009-07-02 http://www.bp-3.com/blogs/2009/06/the-case-against-window-dressing/comment-page-1/#comment-232 Column 2 : links for 2009-07-02 Thu, 02 Jul 2009 17:02:22 +0000 http://www.bp-3.com/blogs/?p=848#comment-232 [...] Process for the Enterprise » Blog Archive » The Case Against Window Dressing Keeping it simple in BPM projects in order to deploy something sooner (or at all). I'm a big fan of this approach, too: simple UIs and simple integration on the first go around, then target the ones that will have the most impact for subsequent deployments. Unfortunately, if you're dealing with an enterprise that insists on having everything in V1 because they usually don't get a V2, it will be hard to break the pattern of over-building. (tags: bpm software development) [...] [...] Process for the Enterprise » Blog Archive » The Case Against Window Dressing Keeping it simple in BPM projects in order to deploy something sooner (or at all). I'm a big fan of this approach, too: simple UIs and simple integration on the first go around, then target the ones that will have the most impact for subsequent deployments. Unfortunately, if you're dealing with an enterprise that insists on having everything in V1 because they usually don't get a V2, it will be hard to break the pattern of over-building. (tags: bpm software development) [...]

]]>