Preference: Agile or Winter fall?

[Former Member]

Hello There.

I need an opinion.

The Business rules Management increase abilities to build applications with comparative less maintenance costs as well are easy to manage. (SAP Life Cycle)

In SAP, There are two I have heared.

1. Agile System.

2. Winter fall System.

Which one is more preffered in the SAP industry?

Why is it so?

I respect your valuable inputs.

Good Luck & Regards.

Harsh Dave

[matt]

Waterfall, I think you mean.

The vast majority of implementations I've been on are Waterfall. Planning, blueprint, realisation, test, go-live.

Nice and easy for PMs.

The most successful, and least stressful project I worked on used this approach only for the configuration of the system, and the ABAP development necessary for that.

For all other developments - Output documents, bespoke reports, bespoke transactions, we had a seperate plan for each - with dates for Functional spec to be ready, development to be ready, testing to be complete.

More difficult to manage, but means that the sourcing levels of developers is more constant - less ramping up and letting go of resources, thereby maintaining continuity, and reducing the risk of not having enough developmers for changing specs, late specified developments etc. It also reduces the need to have a manic two weeks just before the end of realisation, because you have to deliver 10 programs that won't in fact be tested for a couple of months.

[Former Member]

Hello Matthew.

Thanks for Correcting, I mispelled "Waterfall".

Thank you for sharing your great and encouraging experience.

I would like to ask you,

What do you mean by "Bespoke reports and Bespoke Transactions" ?

I will be very glad to know.

Warm Regards.

Harsh Dave

[Former Member]

Hi Dave,

bespoke reports and transactions is a term pretty often used for additional programs Z- or Y- programs and transactions.

Siggi

[Former Member]

Hello Siggi.

Thanks a lot.

Please share your experience or preference for Agile or Waterfall systems?

That'll encourage a lot.

Good Luck & Regards.

Harsh Dave

[matt]

>

> Hi Dave,
> 
> bespoke reports and transactions is a term pretty often used for additional programs Z- or Y- programs and transactions.
> 
> Siggi

Pretty much, yes. Essentially I mean all developments that are not required for business processes, and, to some extent, the developments at the beginning or end of a business process, such as interfaces.

It's not that you leave these to the end, but rather that you plan for them in parallel to the main project timelines.