Yes, it might be applicable to all human resource involved activities with start and finish dates. However, it can't be eliminated fully by the invention of appropriate approach like the critical chain method. I believe there are sufficient ways to prevent this issue from occurring in the project activities by effective training including cross training, communications, performance appraisal, conflict management, work authorization etc. in PMBOK guide. I believe only proactive approach by all project team members can minimize SS in the project. Saving Changes...
Respected Researchers and members of PMI, I am an Infrastructure Engineering and Management student doing my Post graduate in Madurai.I am doing my Project on "CRITICAL CHAIN PROJECT MANAGEMENT IN SCHEDULING CONSTRUCTION PROJECTS". I am in need of help in Data collection for my Projects in any construction companies within Tamil Nadu.
Also I kindly request to suggest me suitable internship program for Critical chain Project Management. Saving Changes...
My experience is that fully communication in and out project team members can reduce the level of SS in a project, but realistically I think that it cannot be eliminated. So, what I do is use every single meeting event by any means to ask about the risks on future tasks and the dependency those tasks have in others. Asking is a mechanism to induce reflexion and facilitate execution, from my perspective. Saving Changes...
Mark HannahBusiness Solution Architect| Hannah Business Intelligence SolutionsIncline Village, Nv, United States
Kanban manages measurable WIP limits and a steady flow of throughput for a primary WBS. If a JIT pivot to market forces (change) arises, a team can flex and with transparency re-prioritize tasks or deliverables to meet expedited finish time/dates. With daily 15 min meetings or real-time retrospectives, lessons learned are audio-recorded, white-boarded with pics, etc. to a knowledge repository, yada yada. Cramming will occur to accommodate a learning curve, spreading the load , and risk management can mitigate and/or remove known risks...cheers Saving Changes...
Denise CantyAgile Coach, Life Coach, Author, Senior Project-Program Manager| Cenden CompanyWashington, Dc, United States
I've never heard the term "student syndrome" either but I never wait until the last minute to do anything that has a deadline. It's too stressful to be a last minute person for myself personally. I do know of others who are do things at the last minute and do a great job. With that said, "to each, his own". Saving Changes...
Suresh KumarAssistant Vice President| Infinite Computers India LtdChennai, Tamilnadu, India
Everyone is a student at some point of time in a project Saving Changes...
Asad AbbasManager Program Management| Publicis SapientBangalore, Karnataka, India
Aug 08, 2016 5:17 PM
Replying to Stéphane Parent
...
Students not only cram at the last minute for an exam, but will crash after the exam. They will need time to decompress and recover.
It's the same thing with your team members. They will spend a lot of time in the last few days to meet the deadline. Give them breathing room afterwards; presume that they will be operating below normal levels.
Students who don't make and follow a plan will always cram and it is not expected from a professional team. Please note that fast tracking and crashing will always increase risk to quality and customer satisfaction. One should always strive to plan, execute and monitor well and do negotiation with customer if the scope of project changes during execution. Saving Changes...
Marcelo GuerraDirector of Engineering| SoundCommerceKirkland, Wa, United States
Yes, 'student syndrome' is everywhere including Project Management. However, it's not a 100% bad thing, a number of the agile practices make good use of this. Saving Changes...
