How do you explain agile process tool (like Scrum or Kanban) to a (traditional) project manager? [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 6 years ago.

Improve this question

I am sure many people involved in the software development projects came up with this question, but I could not actually come up with satisfying answer.

• How to explain to a manager used to having a huge gantt-chart, resource allocation, critical-paths (etc) benefits of using agile process tool such as Scrum or Kanban?

A typical problem is explaining why testing sometimes takes longer than the actually coding...

Answer 1

I'm not sure this is the right forum for this question, but since similar questions are already here, my advice (out of experience) is:

Don't bother explaining. Rather, show him.

In particular, if you want to introduce agile or scrum processes, you'll have to do two jobs: on one side, report him the data he wants (Gantt charts, estimates). On the other, let your team work Scrum without interference. When things go well (they will if your team is with you) you can turn over and say "by the way, this time I managed things this way" and introduce him to agile.

A "traditional" PM is not opposed to process: however, they have probably been around long enough to survive most PM fads and would rather see results than babble.