POSHAK VISHNOIProject management office| Tech Mahindra Ltd.Noida, Uttar Pradesh, India
Hi Pench,
There may be some barriers as below.
1). Project charter and documents are incomplete
2). There is no enough meeting with stakeholders and team members
3). Communications gap
4). Do not have previous or competed projects documents
5). Less resources
6). More paper work causes to time consuming etc.
There may be many more but some points i have described above.
I hope this will be helpful.
...
1 reply by Pench Batta
Oct 05, 2018 10:38 AM
Pench Batta
...
Poshak, Excellent points. Thanks for sharing!
Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Oct 05, 2018 10:32 AM
Replying to POSHAK VISHNOI
...
Hi Pench,
There may be some barriers as below.
1). Project charter and documents are incomplete
2). There is no enough meeting with stakeholders and team members
3). Communications gap
4). Do not have previous or competed projects documents
5). Less resources
6). More paper work causes to time consuming etc.
There may be many more but some points i have described above.
I hope this will be helpful.
Poshak, Excellent points. Thanks for sharing! Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Oct 03, 2018 1:03 PM
Replying to Michael Gabriel
...
Another barrier is not having a platform to hear what your project team (staff, vendors and clients) have to say about how well the project is defined, and how well it is going. Good team dynamics are crucial, and they need to feel that their voices are being heard and actions are taking place, otherwise disgruntlement and ineffectiveness can doom any project. Which is one reason why 50-75% never meet their KPIs.
Mike, excellent points. Thanks a lot! Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Oct 03, 2018 7:13 PM
Replying to Eric Simms
...
I'll add 'poorly defined requirements' and 'failure to identify all stakeholders' to the list. Either one of these will probably doom a project, and they usually aren't detectable until it's far too late.
Eric, both are valid points. Thank you. Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Oct 05, 2018 10:14 AM
Replying to Murtaza Sheikh
...
Absence of clearly defined requirements is no doubt on the top but a close second is the failure to manage stakeholder expectation as you work with those requirements.
If you think about it, its almost an infinite loop. From the inception till the very end, the stakeholders should be given (and consistently reminded of) a very clear idea of what the final result would look like. As PMBOK and most other guidelines would attest, ending a project without delivering anything tangible can also be a success as long as a collective and conclusive agreement is reached with the stakeholders.
Murtaza, agree with your points. Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Oct 03, 2018 7:10 PM
Replying to Rami Kaibni
...
ist of barriers can be endless and it depends on the situation / project but I find communication and lack of transparency are very common.
Yeah, communication is the most the important. Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Oct 03, 2018 3:26 PM
Replying to Anish Abraham
...
I think one of the barrier is lack of clarity. Sometimes employees don’t know or don’t understand the project goals, objectives, roles and responsibilities, etc.
Anish, lack of clarity is always a big barrier. Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States