Final Exam: Software PM Lead

WHAT YOU WILL LEARN

• 

  apply the industry standard amount of time for planning employee availability for capacity planning during the Sprint Planning session
  

  apply the Scrum methodology to a project by defining the Product Backlog, Sprint Backlog, and the Sprint and measuring the Sprint velocity and remaining level of effort using the Burndown Chart
  

  apply the Scrum methodology to prioritize items in the Sprint Backlog and work collaboratively with customers to increase the level of satisfaction with the released product
  

  apply the Traditional Project Management methodology to a project by defining the scope, the work schedule, and measure productivity levels and determine the time to complete the project
  

  apply the Traditional Project Management methodology to a project that has known requirements that will not change to develop a product that will be delivered at the end of the project
  

  describe a method for measuring effort of work for each User Story, remove emotional attachment of dates, has estimates and velocity that are unique per team, and rewards the team for solving difficult problems
  

  describe features of the Increment in Scrum and the criteria to determine when the product is done and releasable as a working standalone product
  

  describe how automated testing allows changes to be tested continuously and how to created a test bed to regression testing
  

  describe how the Sprint Burndown chart is used to show the amount of work remaining, the amount of work done so far and the level of effort remaining to complete the items for this Sprint
  

  describe how the Team Velocity chart can be used to measure the team capacity and show where the team can be improved and stabilized
  

  describe that tasks that are performed during the Daily Scrum and the agenda and responsibilities of the team members
  

  describe the features and purpose of the Sprint Backlog and how it is used during the Sprint to create the product increment
  

  describe the features an purposed of the Sprint Backlog and how it is used during the Sprint to create the product increment
  

  describe the features of the Product Backlog and who it is owned and managed by
  

  describe the fifth principle of Lean, delivering fast
  

  describe the first principle of Lean, eliminating waste
  

  describe the fourth principle of Lean, deferring commitment
  

  describe the purpose and tasks that are performed during the Sprint Retrospective and identify areas of improvement and how to implement those enhancements
  

  describe the relationship between planning and deferring commitment in Lean software development
  

  describe the roles and responsibilities of the Development Team during the Scrum process
  

  describe the roles and responsibilities of the Product Owner during the Scrum process
  

  describe the roles and responsibilities of the Scrum Owner during the Scrum process
  

  describe the second principle of Lean, building quality into products
  

  describe the seventh principle of Lean, optimizing the whole
  

  describe the sixth principle of Lean, respecting people
  

  describe the tasks that are performed by the Scrum Team during the Sprint Planning event and the significance of each task
  

  describe the tasks that are performed by the Scrum Team, the Product Owner and the customers during the Sprint Review event and the significance of each task
  

  describe the tasks that are perfumed by the Scrum Team during the Sprint Planning event and the significance of each task
  

  describe the third principle of Lean, creating knowledge
  

  describe the three major roadblocks that can influence a company's work processes negatively
• 

  describe who is responsible for being the project facilitator, checking equipment before the meeting, ordering drinks and refreshments, bringing supplies to the meeting, checks the team schedules, and tracks the team’s velocity versus
  

  describe who is responsible for defining User Stories, writing acceptance criteria, and determining if the User Story fulfills the product goals
  

  describe who is responsible for representing the customers and end-users, defining the sprint scope, define User Stories in detail, preparing notes for each User Story, and helping to prioritize the Sprint Backlog and the Definition of Done
  

  discover how Scrum practices can help better manage what is being produced
  

  discover how Scrum practices can help in improving quality
  

  discover how Scrum practices for daily Scrums can enable effective meetings
  

  discover how Scrum practices for Retrospective meetings can enable process improvement
  

  explain the problem with giving into pressure in a software development environment
  

  identify aspects of the Agile mindset
  

  identify best practices for improving teamwork in Scrum related activities
  

  identify misconceptions about scrum
  

  identify optimal ways to utilize scrum methodology concepts
  

  identify scrum meetings and how they benefit the business
  

  identify scrum meetings and how they benefit the development team
  

  identify that tasks that are performed during the Daily Scrum and the agenda and responsibilities of the team members
  

  identify the basics of the scrum methodology
  

  identify the features of the Product Backlog and who it is owned and managed by
  

  identify the purpose and tasks that are performed during the Sprint Retrospective and identify areas of improvement and how to implement those enhancements
  

  identify the purpose of various scrum artifacts
  

  identify the tasks that are performed by the Scrum Team, the Product Owner and the customers during the Sprint Review event and the significance of each task
  

  recall aspects of the Agile mindset
  

  recall the traits of various Agile methodologies
  

  recognize the benefits of identifying the seven Mudas of Lean
  

  recognize the challenges in software project development that can be overcome by adopting Scrum
  

  recognize the correct use of scrum practices
  

  recognize the features of Scrum and how it promotes adding value to the development process
  

  recognize the key roles of Scrum projects
  

  recognize the origins of Lean and the seven wastes of Lean
  

  recognize the three key artifacts of Scrum practices which can help improve team performance
  

  recognize the traits of various Agile methodologies