WBS Dictionnary

Hi Sergio
That’s what I was actually doing but every time I start I feel that is a clerical Work that it is better that I do other more imp tasks especially that I’m in the early planning phase.. what do you think ?

Note that I’m still chasing requirements as well as you must probably know most LT think that it takes on’y a project manager to do a project ! So î let you imagine the rest...

Thanks for your input Keith

Thanks Karthikeyan,

In fact I’m using JIRA and the kanban board but what’s the point of the wbs dictionary then ? It’s the reason I’m asking cuz I find that I redo things that might not be probably used especially that when we multiply the tools to be used within a team (and mines are all remote in 6 different countries) that get the stakeholders lost and sometimes less accurate.
Then a question: how do you track all that ? And your status meeting would be based on which input ?

Thanks !

What we try to do is putting clear to eveybody what to do and what does mean. Perhaps this is our case because we are working in virtual highly distributed around the globe environment then we try to avoid too much interaction about basic things that have to be clear from the very begining. So, call it WBS/WBS Dictionary or whatever. Most of the times doing a WBS has no sense mainly when you work with agile based methods. Just in case you are behind the same goal that we are about push people to getting understanding about what to do and what it does means then my recommedation is using the artifact that best fits for that. Obviouly sometimes you are working into schemas where your governance process requires to create some artifacts to get agreement.