The best project approach

[@InfluentialPMO]

If you're managing multiple projects, check out this video: kzbin.info/www/bejne/ooK9p2Ntnr-lZqs

[@EdgarMxCity]

Thank you, could you please tell me what is that book? You mentioned for multiple projects. From my perspective experience; I'm pushing and implementing scrum + kanban (pulling) , and depends on the product agile is much better for SDLC , but waterfall maybe applies more or conventional businesses as construction or that kind of industries. I'm pushing Phase I is for scrum , then optimatation/maintenance Phase II - Kanban. So, we avoid SLA to overkilled the dev team. So. Waterfall according to PMI I only use communication and timeline , risk management face to client, but Scrum for internal efforts.

[@InfluentialPMO]

Hi Edgar, the book on multiple projects is “Managing Multiple Projects” by Elizabeth Harrin. The book you see me taking off the shelf in the ‘training montage’ was “I’d Rather Eat a Cactus Than Manage a Project” by Lesley Elder-Aznar. I little inside joke… 😉

[@EdgarMxCity]

@@InfluentialPMO Thank you!

[@EdgarMxCity]

@@InfluentialPMO a have a question to you, I'm building a Repository of Documents from Different projects (portfolio), depends of the type of PMO we decided *support* so, about documentation, how do you think could be a standard way to structure a Repository if we switch from Scrum to Kanban, and Waterfall to Kanban, or hybrid........

[@Onlinepmcourses]

Agile vs Waterfall creates a false binary choice. Waterfall AND Agile is the right way to go. You are spot-on to note that tailoring is all about selecting the proportions.

[@EdgarMxCity]

Agreed, however, how do you understand Kanban?

[@EdgarMxCity]

I mean , have you ever implemented Kanban?

[@Onlinepmcourses]

@@EdgarMxCity Not on a client project, but I understand it well enough to know where I'd find it useful. What are you thinking of, here?

[@InfluentialPMO]

I’ve used kanban. In fact, I used it today to move this video into the Published column. I use Trello to manage my content and keep track of where things are. I’ve seen kanban boards used well for some teams, but those teams were so well organised I don’t know if I attribute it to kanban. It was just a tool used well to good effect.

[@InfluentialPMO]

Thanks Mike - I think we’re on the same page with this. 👍 I suggested that people will need to become skilled in many methods - but do you see a time where the training courses will become hybrids too rather than waterfall, agile, etc?

[@GregPreece]

Cool video Stuart. Love the intro. It would have been cool to see some text when you were explaining the difference between agile and waterfall to make it easier to understand the differences. Great to see Guy's breakdown!

[@InfluentialPMO]

Noted! I’ll use that for when I do the full definitions of each method. Thanks for the feedback!

[@saudpm40]

Well, it depends upon the industry as to which approach to adopt. For construction projects, we go for Waterfall and for IT projects we settle with Agile. I have served a decade leading projects in Waterfall approach so I am comfortable with it :) In IT the projects are incremental and require a lot of iterations

[@EdgarMxCity]

Depends on the type of the project - strategy goes with Waterfall , tactical goes much better for scrum. Fist focus on the project cycle , and second focus on the product / software development.

[@grahamgoodwin6880]

One of the benefits of Agile that I don’t think particularly gets addressed in waterfall projects is the focus in skills development within agile teams. Whether it is the scrum master, stand ups or retrospectives the identification and opportunity to address within the project makes long term agile teams very effective and I don’t see the same in waterfall.

[@InfluentialPMO]

That’s a great point Graham; I hadn’t considered that. Good shout 👍

[@danielmunoz8697]

There is no such thing as "waterfall vs agile". In fact, both are not methodologies, nor methods.