Product Operations Program ManagerBarcelona, Cataluña, Spain
There is not a rule that applies to all, but in my case I do update them once a week (team members also write time on a weekly basis). Saving Changes...
The Gantt chart usually gets updated once per week because that's the management review cycle. When there are actions that need to get managed more closely than that, I typically use what we called a Detailed Action Plan (DAP). Which is essentially a network diagram of tasks. Saving Changes...
DORA LUZ MejiaCEO| IT ExploreEnvigado, Antioquia, Colombia
for large projects I use to update every 2 weeks in a review with the main team afther the sprint review. for medium I update every week and for small ones (3 months) i update twice per week.
if you are in an pure agile environment i have found the sprint review the point to update. Saving Changes...
Depends on the level of control required for the project. If you have a competition to build a house in one day you might check your schedule hourly or more frequently whereas a mega project might be updated biweekly or monthly even. Saving Changes...
alan rossneyProject Manager| jacobs EngineeringDublin, Dublin, Ireland
facility design and installation projects need an updated gantt each week. with a collaborative planning tool like Smartsheets team members can update their activities themselves. For software development projects team members should be updating their tasks every two days on JIRA or whatever. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
I suppose, and what I hear above, it comes down to on an as-needed basis. Those needs are specific to the organizations, projects, and agreed-upon terms for updates, both the project team and stakeholders. Saving Changes...
"Ambition is like a frog sitting on a Venus Flytrap. The flytrap can bite and bite, but it won't bother the frog because it only has little tiny plant teeth. But some other stuff could happen and it could be like ambition."