I'm not sure about new tasks, but certainly the servant-leader requires effective and careful delegation of many tasks, and some that are not even delegated but left to the dev team who are in effect in charge of themselves. The challenge is swapping between both waterfall and Agile projects, and thus swapping hats and sometimes personalities...
First, take into account that something like Agile something does not exists. You can apply Agile which any type of life cycle process. If you are talking about methods based on Agile then you have methods where the project manager role is defined (DSDM), other where you will find that project manager role could be shared by two roles (Scrum framework where some people consider that project manager role is taking by Scrum Master role) and others. My recomendation is taking a look to PMI´s Agile Practice Guide and PMI´s Software Extension Guide.
Certain practices which a PM might be used to such as assigning tasks, developing a detailed schedule, or following up explicitly with team members on progress will morph or evolve, but the essence of project management does not change. In fact, knowledge areas such as risk management, stakeholder management & communications management need to be elevated to successfully manage projects where value is delivered earlier and frequently.
Kiron
...
2 replies by Jim Sass, DBA and Nancy Avila
Jan 25, 2018 12:35 PM
Jim Sass, DBA
...
Well said Shivanjali. I get the feeling from numerous articles I read that many people think it's an either or thing (waterfall or agile) when in fact it is in truth more of a hybrid.
Feb 14, 2018 3:22 PM
Nancy Avila
...
Dr. James Sass: Would you say it was because of the time dependency? The one with critical lead time tends to fall more on the hybrid method.
Certain practices which a PM might be used to such as assigning tasks, developing a detailed schedule, or following up explicitly with team members on progress will morph or evolve, but the essence of project management does not change. In fact, knowledge areas such as risk management, stakeholder management & communications management need to be elevated to successfully manage projects where value is delivered earlier and frequently.
Kiron
Well said Shivanjali. I get the feeling from numerous articles I read that many people think it's an either or thing (waterfall or agile) when in fact it is in truth more of a hybrid. Saving Changes...
Anonymous
Jan 23, 2018 7:29 PM
Replying to Sante Vergini
...
I'm not sure about new tasks, but certainly the servant-leader requires effective and careful delegation of many tasks, and some that are not even delegated but left to the dev team who are in effect in charge of themselves. The challenge is swapping between both waterfall and Agile projects, and thus swapping hats and sometimes personalities...
thank you!
Saving Changes...
Anonymous
Jan 23, 2018 7:33 PM
Replying to Sergio Luis Conte
...
First, take into account that something like Agile something does not exists. You can apply Agile which any type of life cycle process. If you are talking about methods based on Agile then you have methods where the project manager role is defined (DSDM), other where you will find that project manager role could be shared by two roles (Scrum framework where some people consider that project manager role is taking by Scrum Master role) and others. My recomendation is taking a look to PMI´s Agile Practice Guide and PMI´s Software Extension Guide.
One of the main challenges is that Agile, as opposed to more traditional methodologies, welcome changes. As a Scrum Master you may need to be in the middle of constant changing priorities and being aware of not losing focus on the ultimate project objective.
...
1 reply by Sergio Luis Conte
Feb 03, 2018 6:44 AM
Sergio Luis Conte
...
Jose Luis, into all method changes are welcome. It is impossible do not do that in actual world. But the change control process must be defined. Including Scrum the change control process is there. Using Scrum you can not put changes in place as people want, you "paid" for that. Some people think that thanks to using Agile based methods they can change everything at anytime. That is totally wrong.
One of the main challenges is that Agile, as opposed to more traditional methodologies, welcome changes. As a Scrum Master you may need to be in the middle of constant changing priorities and being aware of not losing focus on the ultimate project objective.
Jose Luis, into all method changes are welcome. It is impossible do not do that in actual world. But the change control process must be defined. Including Scrum the change control process is there. Using Scrum you can not put changes in place as people want, you "paid" for that. Some people think that thanks to using Agile based methods they can change everything at anytime. That is totally wrong. Saving Changes...
Certain practices which a PM might be used to such as assigning tasks, developing a detailed schedule, or following up explicitly with team members on progress will morph or evolve, but the essence of project management does not change. In fact, knowledge areas such as risk management, stakeholder management & communications management need to be elevated to successfully manage projects where value is delivered earlier and frequently.
Kiron
Dr. James Sass: Would you say it was because of the time dependency? The one with critical lead time tends to fall more on the hybrid method.
...
1 reply by Jim Sass, DBA
Feb 15, 2018 11:04 AM
Jim Sass, DBA
...
I am finding that many organizations want to try Agile because it's the latest buzz word but they are tied to waterfall so they end up with a hybrid that mostly works for them. In other cases, waterfall makes sense for part of the project and agile works for other parts. That's not to say there is not a case for purely waterfall or agile--there is.
Dr. James Sass: Would you say it was because of the time dependency? The one with critical lead time tends to fall more on the hybrid method.
I am finding that many organizations want to try Agile because it's the latest buzz word but they are tied to waterfall so they end up with a hybrid that mostly works for them. In other cases, waterfall makes sense for part of the project and agile works for other parts. That's not to say there is not a case for purely waterfall or agile--there is.
...
1 reply by Kevin Drake
Jul 05, 2018 6:36 PM
Kevin Drake
...
I have seen it in many organisations and I agree with you.
