The Art and Science of Leading Projects
teamgantt.com
The Art and Science of Leading Projects
1–10 of 23 posts
Re: The Art and Science of Leading Projects
#2TeamGantt is a great help for planning, and this course is well worth doing.
In my team's recent planning of a major multi-month feature, TeamGantt tooling helped us plan, helped our leadership visualize milestones and goals, and helped our developers deliver on time and on budget.
Re: The Art and Science of Leading Projects
#3Not for me, but I do like that one of the sections is:
> 08 - Winning trust with communication
> Learn simple keys to becoming a better communicator and how to identify your team’s different communication styles.
Having experienced the pain of working somewhere where leadership tried to decree a single "right" method of communication for all developers that didn't jive with us at all, I don't take this for granted anymore.
In that case, management declared that in-person communication was so essential to the agile philosophy that all devs should be ok with being interrupted by anyone and at any time for the purposes of having a face-to-face chat (and WFH was not allowed unless sick). I now work somewhere where I don't see any co-workers in person on most days, and somehow we get tons more work done and stay in contact just fine. Weird how that works...
Re: The Art and Science of Leading Projects
#4Not for me, but I do like that one of the sections is: > 08 - Winning trust with communication > Learn simple keys to becoming a better communicator and how to identify your team’s different communication styles. Having experienced the pain of working somewhere where leadership tried to decree a single "right" method of communication for all developers that didn't jive with us at all, I don't take this for granted an…
People constantly confuse communication with a lot of talking and collaboration with sitting in the same room or constant meetings.
Re: The Art and Science of Leading Projects
#5TeamGantt is a great help for planning, and this course is well worth doing. In my team's recent planning of a major multi-month feature, TeamGantt tooling helped us plan, helped our leadership visualize milestones and goals, and helped our developers deliver on time and on budget.
your comment history luckily proves you are not a sock puppet :)
but this comment is still suspiciously smooth
Re: The Art and Science of Leading Projects
#6The book "Project Management for the Unofficial Project Manager" is a high-level but pretty complete introduction to project management. It has good examples from non-technical projects, such as rolling out a new health program in a hospital. It uses official terms from the Project Management Institute’s infamous "Project Management Body of Knowledge" (PMBOK) so information learned from this introduction can be carried over to more rigorous projects.
Re: The Art and Science of Leading Projects
#7Step 1 is not using a gantt chart to create some illusory impression of knowing exactly how complex projects will unfold.
Re: The Art and Science of Leading Projects
#8Step 1 is not using a gantt chart to create some illusory impression of knowing exactly how complex projects will unfold.
Eh, I would say creating one (or something similar) is a useful exercise to help break up large tasks and think more thoroughly about how to split work within a team. It also helps to highlight possible bottlenecks and is a useful visualization so everyone on the team is on the same page.
Re: The Art and Science of Leading Projects
#9TeamGantt is a great help for planning, and this course is well worth doing. In my team's recent planning of a major multi-month feature, TeamGantt tooling helped us plan, helped our leadership visualize milestones and goals, and helped our developers deliver on time and on budget.
your comment history luckily proves you are not a sock puppet :) but this comment is still suspiciously smooth
and how does he know the course is worth doing since only classes 0, 1, 2 of 14 are released.
Re: The Art and Science of Leading Projects
#10Step 1 is not using a gantt chart to create some illusory impression of knowing exactly how complex projects will unfold.
Eh, I would say creating one (or something similar) is a useful exercise to help break up large tasks and think more thoroughly about how to split work within a team. It also helps to highlight possible bottlenecks and is a useful visualization so everyone on the team is on the same page.
Agreed. I love gantt charts because they show where things have to come together. I rarely give time estimates when asked but I always ask when something is needed from me to not hold up other people.