I build agentic revenue systems for Fortune 50 companies
Risk vs Issue is something that confuses us more than anything else in Project Management. I have myself always been confused about the difference between Risk and Issue. I always understood it as Issue is an event and Risk is the Consequence. I believe that most of us in the profession also think the same way. So I am not wrong…until I read the definition in PMBOK.
I receive numerous emails about the best ways to get PDUs to renew the PMP certification. Here is the best guide resource for Free PDUs for PMP renewal:
http://pmzilla.com/24-real-methods-get-your-free-pdus-pmp-pmirmp-pmisp-pmiacp-etc
This is the best…
Every time I create a new MPP, I ask this question to myself “How and where to start?”. I very well remember the first time I created a Microsoft project plan and I was struggling on strategy to put a plan in place. There was nobody to mentor me. It is very essential that we start right. Here is what I found very useful for me:
There is a very good tutorial on creating Microsoft Project Plan with the similar approach at http://office.microsoft.com/en-us/project-help/create-a-project-plan-in-5-easy-steps-HA001136153.aspx
Thanks
Rohit Prabhakar, PMP
As per me in the current technology world, managers with strong technology background are more equipped to challenge teams to higher productivity levels and lead by example. I have been watching this and trying to gather data for myself from all different clients and offices I have worked in last few years. Everywhere I have seen that managers with strong technology background have more hold on the project and are more clear in their communication as they know what exactly is going in the team. From team’s side they know that there is a place they can go in hour of need hence leading to better relationship with the Manager.
This is my opinion, what is yours?
Let me ask the question again:
I have been reading various forums for a long time and finally decided to get PMP done few weeks ago. Here is my schedule of action with exact dates on my journey for the project management certification:
August 19 2010:::: Enrolled for the PMStudy class for PMP in Milwaukee, WI, USA
August 20 2010:::: Not yet started the online study material for PMP
August 21 2010:::: Started with the online study material for PMP exam. The only thing I did that day was to memorize the process chart and the formulas provided by PMStudy. (Excellent chart from PMStudy)
August 22, 2010:::: Practiced the process chart only once
August 23, 2010: PMStudy class 8 AM to 6 PM (I had an excellent coach, Mr.Mike Tomaszewski , PMP. Learning was fun!), followed by 3 hrs of study at home (same as taught in class and few practice tests provided in the course)
August 24, 2010:::: PMStudy class 8 AM to 6 PM, followed by 3 hrs of study at home (same as taught in class and few practice tests provided in the course). I am excited to become PMP certified.
August 25, 2010:::: PMStudy class 8 AM to 6 PM
August 26, 2010:::: PMStudy class 8 AM to 3 PM, followed by 5 hrs of study at home (all processes and few practice tests provided in the course)
August 27, 2010:::: Reread all the important as marked as instructed by Mike in the PMStudy book. Took 2 practice test ( 200 question, provided by PMStudy). Practiced the Process Chart and formulas 2 times. Checked ITTOs for Risk, Procurement and Quality. Watched a movie.
August 28, 2010:::: Took 1 practice test ( 200 question, provided by PMStudy). Practiced the Process Chart and formulas 1 time. Checked ITTOs for Risk, Procurement and Quality once again. Watched a 2 movies (1 in noon and 1 evening!@home). Got to bed at 10 (As advised by Mike and PMStudy, 12 hrs rest and no study before the exam)
August 29, 2010: Reached the Prometric testing center @ 8:45 AM. Test started at 9:30, completed 1st round with 75 marked for review in 2:15. Then took 1:15 to review all 75 and finally the rest of the time to re-review the marked ones that I was super confused about. System had to force time out for me :o) and then the blank screen came
In last few days I have compiled some information on SCRUM in separate articles. Here is the consolidation of all the links:
![Reblog this post [with Zemanta]](https://img.zemanta.com/reblog_e.png?x-id=c93887db-65d5-4c5b-8358-6304d70b1f3e "SCRUM Series 3")
Scrum has been successfully used for projects with 500+ team members lots of time. As SCRUM can only last for 15 minutes and some other similar rules hence in order to scale the SCRUM for bigger team we can use SCRUM OF SCRUMS. Based on the type of work the scrum team is constituted for every 7 to 10 team members having a Scrum master and the Product Owner. After the first lever team SCRUMS we have SCRUM of SCRUMS and there could also be more level of SCRUM OF SCRUMS.