Did you know that we are all using 𝐀𝐠𝐢𝐥𝐞 𝐌𝐞𝐭𝐡𝐨𝐝𝐨𝐥𝐨𝐠𝐲 of Project Management though we think that we use only 𝐓𝐫𝐚𝐝𝐢𝐭𝐢𝐨𝐧𝐚𝐥 𝐦𝐞𝐭𝐡𝐨𝐝𝐨𝐥𝐨𝐠𝐲 ?

Day 2 𝐨𝐟 30
𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐚𝐥 𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 𝐋𝐞𝐬𝐬𝐨𝐧𝐬 !
.
.
“𝘘𝘶𝘪𝘵 𝘔𝘦𝘥𝘪𝘰𝘤𝘳𝘪𝘵𝘺, 𝘉𝘶𝘪𝘭𝘥 𝘵𝘩𝘦 𝘗𝘩𝘢𝘳𝘮𝘢 𝘓𝘦𝘨𝘢𝘤𝘺”
I was in job for last 20 years, but today I have started my successful startup, if you want to know the secret on how you can also do the same, then DM to understand more about it.


When I started my career as Trainee at Cadila Pharma at Dholka, Gujarat, I was not aware that Project Management skills will be so important to learn and master.
In fact many of the Pharma/Biopharma Professionals are doing project without actually applying all the best practices to be used for Project Management. Never mind 😂 as I was also one of them until I became PMP® Certified Professional.

We all use Agile Methodology in Traditional Projects :-
1. 𝐔𝐬𝐞 𝐨𝐟 𝐊𝐚𝐧𝐛𝐚𝐧 𝐁𝐨𝐚𝐫𝐝 :- Displaying all the project information on one board with What’s To Do list, What’s in Progress and What are the things done. This is what almost all project manager uses in their respective projects.
2. 𝐔𝐬𝐞 𝐨𝐟 𝐃𝐚𝐢𝐥𝐲 𝐒𝐭𝐚𝐧𝐝𝐮𝐩 𝐌𝐞𝐞𝐭𝐢𝐧𝐠 :- While we say different names for this meeting i.e Daily PD (performance dialogue) meeting, Daily Update Meeting, Daily Morning Meeting etc. The purpose of this meeting is to understand the progress. And we precisely ask 3 questions in this meeting. Please write in comment which 3 questions should be discussed in Daily Standup Meeting.
3. 𝐁𝐮𝐫𝐧𝐮𝐩/𝐁𝐮𝐫𝐧𝐝𝐨𝐰𝐧 𝐂𝐡𝐚𝐫𝐭 :- As this name suggest, we are not burning anything here 😂. This chart shows the progress of the project activities. Basically this is being used in software development to track the number of user stories. (to understand more about user stories, please check my next post on user stories). The chart can be used to track in traditional approach. Example I gave in my earlier post – Burndown Chart for Civil activities. (https://lnkd.in/dp9RaeTu).
4. 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐁𝐚𝐜𝐤𝐥𝐨𝐠 :- This name is suggesting to keep product in backlog😂. Not really. Basically this is used to identify total number of user stories to complete to ensure product get released. The same in traditional approach is User Requirement Specification (URS) or simply Requirement document.

If I start writing on this, this list can go for long, so if you are someone wants to learn more about it, and wants me to guide you to build thriving career in pharma then do let me know by dropping comment “PAMC”.
and I will give you my secret on how I have developed pharma career in last 20 years.

#career #projects #pharma #pharmaworld #pharmaceuticals #agilehashtag#traditional #legacy #gauravdakshini