Final Exam: Software Project Requirements & Design with Agile

WHAT YOU WILL LEARN

• 

  Recognize how functional requirements differ from non-functional requirements
  

  describe in detail the requirements management process
  

  describe how to use the story points estimation method in agile
  

  describe how to use the planning poker estimation method in agile
  

  describe using examples the best practices of using modularity in agile software design
  

  recognize how agile tools such as initiatives, themes, epics, and stories help define and manage scope better than traditional methods for scoping
  

  describe the best practices to be adopted for building an agile culture in the organization
  

  recognize how to build product vision from a requirement or objective of the software product
  

  recognize the challenges faced in transforming to an agile organization
  

  describe using examples the best practices of using coupling concepts in agile software design
• 

  describe the minimal viable product
  

  recognize how to generate user stories from a requirement or objective of the software product
  

  describe what functional requirements are and how they are used in a software project
  

  discover the benefits offered by agile estimation models over traditional estimation methods
  

  recognize what software requirements are and their importance in successful software project management
  

  describe what non-functional requirements are and how they are used in a software project
  

  describe the importance of agile software requirements
  

  describe how to use the dot voting estimation method in agile
  

  define what the definition of done means in the scrum framework using examples
  

  describe how to use the bucket system estimation method in agile