Please login or join to subscribe to this thread
What methodology are you using to run the project? If this is an Agile SCRUM approach, a daily stand up will allow you to gain this information. You need to ask 3 questions:
What have you completed since the last meeting?
What do you plan to complete by the next meeting?
What is getting in your way?
This will allow you to ensure progress is as expected, the team velocity is on track to deliver the outputs and also address anything that could cause issues/delays.
Interesting your question
Thanks for sharing
Recently there was a reflection on the pros and cons of the daily meeting:
Regarding the status reports two issues:
1. What do your key stakeholders say about the frequency and content of the reports?
2. What project management support technology do you use?
- Allows you to track the performance of online projects?
- Does it enable data collection to produce status reports according to the wishes of the main stakeholders?
Without making any assumptions on any given approach, having an open line of communication with the team is a gateway for success. To do so, the team ideally would have insight into the needs, intent, and goals of the project, with clear expectations of the work and the manner in which the work is done. In short, empower the team to be successful, to make decisions, to do the work, and to showcase their skills and experiences.
A couple of ways to have this open line of communication could be through a daily brief cadence of meetings, i.e., daily huddle, along with a centralized project space to share to expose all information and knowledge around the project. Lastly, some capability such as MS Teams or Slack to enhance the communication framework.
While it depends on the culture of your organization the worst thing you can do is try to obtain daily updates for a project. Why? Because activities has a duration then the updates must be scheduled taking into account the duration. Just in case you use agile based methods then depending on the associated life cycle you have to perform or not daily meetings but is not for getting update like in other approches is more with focus on removing stone in the road.
Regardless of the life cycle used, if the team is fairly small and working collaboratively together, you could use a work board (e.g. To Do, In Progress, Blocked, Done) as a quick means of gauging work item status without adding administrative effort on everyone's plates. That, combined with daily standups can provide a good sense as to what is going on.
I agree with Sergio. It depends.
Its best to do an informal connect with team to understand concerns before they become issues.
A weekly formal status/progress call is what I practise with my virtual team setup
Currently I'm doing the same worst thing which you have mentioned here, by going to person to person for getting updates.
Still I am not getting accurate updates or I'm getting updates after completion of Task or adding Task to update my Daily Progress report.
Here you mentioned "to use agile based methods" can you brief me more about this...???
My Own Views on Daily/Weekly/Monthly Meetings:
A Meeting with Some Proper Agenda / Subject / Topic which helps to resolve issue, or clear the holistic picture which helps and improves entire Project team where they are is necessary.
I've seen some of the meeting which doesn't have any agenda or subject but just to show to the management or to impress the Bosses, and in this meeting they don't have any topic is to discuss, Just waste of time and energy of Team. Or having some Refreshment.
So Meeting must be very clear and strict to the Subject /Topic/Agenda to discuss,
Only meeting related people are Invited for discussion.
Clear the focal points or show every Team member has a Clear picture what He/She has to do on particular issue / scenario.
resolve the issue and at least have some conclusion which clears the entire Project Team.
At the End of meeting everyone is very clear for their Response. because MOM is noted and everyone has their names in Action Taken by (the Person Name)
Please login or join to reply