Brian Pan - Notes on PM and Agile

 Notes from here  There are 10 knowledge areas, as outlined in PMBOK 6, that are to be remembered sequentially. It is presented in logical order (with exception to Stakeholders which is tacked on at the end).  Integration: In other words, you can’t ‘do’ schedule management and ignore what the impacts of that might be on people, risk, communications, cost and the rest. Scope: Knowing what the project will deliver Schedule: all about making a detailed plan to tell everyone when the project will deliver what is in the requirements. Cost: Managing project fund Quality: Although quality varies project to project and many aren't as regimented, it is important to be aware and use appropriately Resource: Working out the resources needed to get the project done Communication: Creating a communication plan and monitoring for adjustments Risk: Covers an adequate overview of managing risks  Procurement: Depending on any purchases involved, there is a lot of contracting and negotiation Stakehol

 Original article here 1 - Initiating - This is where the project is formally authorized by the sponsor, initial scope defined, and stakeholders identified. - It is important that the PM is formally authorized at this point, as PMs have a lot of accountability and little authority.  2- Planning  - PMBOK outlines 24 discrete processes involved in planning  - Significant idea is to think through the process in advance 3 - Executing  - Since the project team is important in execution of the process, it is also important that cultivating the team is as well. 4 - Monitor and Control - One way to think about monitoring and controlling is to imagine that you were driving across the country according to your plan or a roadmap. But if you got lost and you didn't have a GPS you'd stop, ask for directions and get back on track, or maybe based on new information, such as a new road that would cut hours off the trip, you'd change or update your plan. 5 - Closing  -  The project manage

 Notes from here A form is a tool you use to record a single item - issue, change, problem, idea, etc. It gives it representation and acknowledges its existences A lot is list of all the items.  Having records of forms/logs promotes transparency and mutual understanding. It also serves as a reference for later use.  Many projects will have more items to track than originally anticipated, so plan for volume in tracking from the beginning.  Risk is a concern regarding the future. It is a comprehensive study resulting in a pillar known as Risk Management.  Issue is a concern of something in the present. It's happening now. Change affects things in the past. It is synonymous with scope management. The three may introduce new risk/issue/changes to each other, so it is important to be able to cross-reference.  Tasks should not be kept in logs, but incorporated into WBS and Project Schedule.  Management Process:  Plan for various items. Determine how to log. Document approach and estimate

 Notes from  here There are five phases of project management. 1. Project Initiation  Here, you are turning an scribble into a meaningful SMART goal. Business case is defined broadly and the project charter is created. Included within the cater is the goal, scope, key stakeholders, and register of roles. Technical aspects are not yet considered yet at this stage. 2. Project Planning  The project road map is planned out. Unless it is agile, this phase is very comprehensive and may account for up to 50% of the project's time. It includes identifying technical needs, developing a detailed project schedule, creating a communication plan, and setting up goals/milestones/deliverables.  3. Project Execution  Deliverables are being met.  4. Project Monitoring and Controlling Simultaneous with Step 3, PM makes sure that project objectives are being met and everything is good smoothly between the team and stakeholders. PM ensures that there is minimal deviation from the plan and establishes

 The common SMART goal seems to be very well spoken of and probably crossed your ears a few time. It stands for Specific, Measurable, Attainable, Relevant, Time-based. While they might be quite useful in defining the goal, like all things, it needs an occasional update. Here steps in the CLEAR goals.  CLEAR goals are an agile counterpart to SMART goals. It stands for Collaborative, Limited, Emotional, Appreciable, Refine-able.  Collaborative - Who is on the team and WHY do these collaborators matter? Limited - What are the boundaries? When do you start/stop? And to what scale is or isn't the project? Emotional - How does this goal make a connection with you/your team? Is it meaningful? Does it provide any personal satisfaction? What of the atmosphere? Appreciable - What is the next action? Milestone?  Refineable - What can I anticipate changing? What may go wrong? How would you adapt? An example that I briefly scriblbed:   I will have lunch with my boss at Panera Bread next year to