Project+ Extra 17 Flashcards
??? project schedule network diagramming method that uses rectangular boxes/nodes to represent activities and arrows to represent precedence relationships between activities.
PDM :
Summary Activity : group of related activities is shown as single aggregate activity in bar chart or graph. Have own internal sequence of activities.
Loops : activity sequences that must be revisited or repeated.
Conditional Branches : activities that’ll be implemented only under specific conditions.
info
??? any network diagramming method that allows for non-sequential activities like loops or conditional branches. Represented by rectangles, decision points represented by diamonds, and directional flow by arrows.
Conditional Diagramming Method :
??? management approved version of project schedule, drawn from schedule network analysis and includes baseline start and finish dates. Provides basis for measuring and reporting schedule performance, formal part of project management plan.
Schedule Baseline :
??? working product after each 2-4 weeks iteration w/increased functionality is shared w/client for feedback. Frequent feedback sessions allow developers to continuously improve product and reduce risk w/product development. Teams are involved in project right from planning stage and are responsible for estimation. PMs shift roles to become a facilitator.
Agile Project Management :
??? focuses on iterative and incremental delivery of products. Simple approach, high productivity, and scope for applicability to multiple areas. Create product by using customer requirements as starting point. List is then shared w/team, which then breaks each requirement into sub-tasks. And each team member begins work on sub-tasks, gives an estimate. As sections of product are created they’re shared w/client for review/approval.
Scrum :
??? are customer requirements and features. Each user story emphasizes functionality of feature and how it adds to final product. User stories can vary in size/complexity.
User stories (Scrum) :
Product Owner : individual or org. responsible for gathering inputs about a product from customer and translating requirements into product vision for team/stakeholders.
Scrum Master : individual who serves, protects, and supports team like a coach or facilitator and works closely w/PO but does not control Scrum team. Can be part-time or fulltime.
Scrum Team : dedicated, self-managing, cross-functional, fully empowered individuals who deliver finished work required by customer.
Scrum :
??? prioritized list of customer requirements and 1st step of Scrum. Priority based on riskiness and business value of user story. PO creates Product Backlog based on user story, w/input from each stakeholder including team, customer, end users and other interested parties.
Product Backlog
??? list of user stories from PB that Scrum Team chooses and commits to complete in that Sprint cycle. Used to create Deliverable at end of cycle. If customer requirements changes or PO identifies any extra stories, they’re added to PB and not SB.
Sprint Backlog :
