Project Management

Please login or join to subscribe to this thread

The difference between the AGILE and SCRUM methodologies. I am not too clear. Can someone help illustrate in practice?

linkedin twitter facebook  
avatar
SAMUEL ODJELUA Msc, PMP, PMI-RMP, PMD Pro 1&2| THE LANDS COMMISSION, ACCRA - GHANA Accra, Spintex, Ghana
I have never practiced them and i want to be familiar with how they operate before i find myself in that environment. I will b most grateful my seniors.
Sort By:
< 1 2 3 >
avatar
vijendra kumar Project leadership| LARSEN AND TOUBRO INFOTECH Mumbai, Maharashtra, India
really nice and informative
avatar
Farouq Zaabab Researcher, Coach, Trainer, Consultant| Freelancer Sohar, Oman
My esteemed colleagues said it all. Agile is a family and Scrum is one member. This family shares a set of four core values and twelve principles (outlined in the agile manifesto here https://www.projectmanagement.com/wikis/481211/Agile-Manifesto).
avatar
Handi Taruvinga I.T Solutions Architect| Consultant Mbabane, Hhohho, Eswatini
The responses are right on point. Those two terms where confusing me as well.
avatar
Adrian Carlogea Australia
To make things more complicated Scrum in software development is used also in non-agile (waterfall) projects.

I have seen this happening in the following scenario:
- The customer wants the delivery of the software in one-go or eventually in two or three releases, the first one delivering the bulk of the functionality while the others some additional features. In principle the customer wants a waterfall project.
- The software company is used to use Scrum and is using it in all circumstances even if the project is waterfall.

Is this project Agile or not?
...
1 reply by Wade Harshman
Oct 04, 2019 9:15 AM
Wade Harshman
...
A scrum team will work to deliver a potentially shippable product increment in each iteration. At the end of each iteration, they will review that increment with the customer and get feedback before planning the next iteration.

When that product gets released is up to the customer or some designated stakeholder (perhaps the Product Owner). This doesn't make the project a "waterfall." They're just managing releases.
avatar
Wade Harshman Scrum Master| GDIT Indianapolis, In, United States
Oct 03, 2019 7:29 PM
Replying to Adrian Carlogea
...
To make things more complicated Scrum in software development is used also in non-agile (waterfall) projects.

I have seen this happening in the following scenario:
- The customer wants the delivery of the software in one-go or eventually in two or three releases, the first one delivering the bulk of the functionality while the others some additional features. In principle the customer wants a waterfall project.
- The software company is used to use Scrum and is using it in all circumstances even if the project is waterfall.

Is this project Agile or not?
A scrum team will work to deliver a potentially shippable product increment in each iteration. At the end of each iteration, they will review that increment with the customer and get feedback before planning the next iteration.

When that product gets released is up to the customer or some designated stakeholder (perhaps the Product Owner). This doesn't make the project a "waterfall." They're just managing releases.
...
1 reply by Adrian Carlogea
Oct 04, 2019 4:34 PM
Adrian Carlogea
...
On the project on which I worked the customer had both a project director and a project manager and they planned the project as any other waterfall project. The business was involved only at the beginning when the requirements were defined and then at the end during user acceptance testing.

Despite this the software company still used Scrum but nobody from the customer reviewed what was "delivered" after each sprint. The customer didn't care about the sprints at all. Scrum was just used internally by the software development company to plan their work with no input from the customer.

At that time another project was in progress that used Agile. After a while the business said that they can't commit resources to be involved in the planning and reviewing the iterations so the project ended up a fiasco. When the business backed up the team did not have waterfall like requirements to continue the work. The project ended up costing huge sums of money and delivered very little.

The waterfall project also ran over budget but in the end delivered and was very well received by the business. It would have been even better if the software company wouldn't have used Scrum internally for development.
avatar
Adrian Carlogea Australia
Oct 04, 2019 9:15 AM
Replying to Wade Harshman
...
A scrum team will work to deliver a potentially shippable product increment in each iteration. At the end of each iteration, they will review that increment with the customer and get feedback before planning the next iteration.

When that product gets released is up to the customer or some designated stakeholder (perhaps the Product Owner). This doesn't make the project a "waterfall." They're just managing releases.
On the project on which I worked the customer had both a project director and a project manager and they planned the project as any other waterfall project. The business was involved only at the beginning when the requirements were defined and then at the end during user acceptance testing.

Despite this the software company still used Scrum but nobody from the customer reviewed what was "delivered" after each sprint. The customer didn't care about the sprints at all. Scrum was just used internally by the software development company to plan their work with no input from the customer.

At that time another project was in progress that used Agile. After a while the business said that they can't commit resources to be involved in the planning and reviewing the iterations so the project ended up a fiasco. When the business backed up the team did not have waterfall like requirements to continue the work. The project ended up costing huge sums of money and delivered very little.

The waterfall project also ran over budget but in the end delivered and was very well received by the business. It would have been even better if the software company wouldn't have used Scrum internally for development.
< 1 2 3 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"The man who views the world at 50 the same as he did at 20 has wasted 30 years of his life."

- Muhammad Ali

ADVERTISEMENT

Sponsors