Aspire Agile for Software Development Agile for Software Development Track 2: Software Requirements & Design with Agile
Final Exam: Software Project Requirements and Design with Agile will test your knowledge and application of the topics presented throughout the Software Project Requirements and Design with Agile track of the Aspire Agile for Software Development Journey.
| Objectives |
Final Exam: Software Project Requirements & Design with 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
- Describe how to use the dot voting estimation method in Agile
- Describe how to use the planning poker estimation method in Agile
- Describe how to use the story points estimation method in Agile
- describe in detail the requirements management process
- describe the best practices to be adopted for building an Agile culture in the organization
- describe the importance of Agile software requirements
- describe the Minimal Viable Product
- describe using examples the best practices of using coupling concepts in Agile software design
- describe using examples the best practices of using modularity in Agile software design
- describe what functional requirements are and how they are used in a software project
- describe what non-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 how Agile tools such as Initiatives, themes, epics, and stories help define and manage scope better than traditional methods for scoping
- Recognize how functional requirements differ from non-functional requirements
- recognize how to build product vision from a requirement or objective of the software product
- recognize how to generate user stories from a requirement or objective of the software product
- recognize the challenges faced in transforming to an Agile organization
- Recognize what software requirements are and their importance in successful software project management
|
