IT Professional Curricula     Business Skills for the IT Professional Solution Area     Project Management     Software Project Requirements and Design with Agile

---

Being able to gather software requirements quickly is a crucial component of the software development life cycle. Sadly, traditional software requirements are static and do not respond well to change and are not very effective. Agile software requirement methods can be used to create requirements that adapt to change and are highly effective in creating software that will satisfy customer needs.
In this course, you'll learn the differences between software requirements, functional requirements, and non-functional requirements. You'll examine the shortcomings of traditional requirement specification and the traditional management process. Finally, you'll learn about Agile software management, Agile software requirements, the software requirements specification document, and the software feasibility tool.

---

---

Objectives

Agile Software Projects: Software Requirements discover the key concepts covered in this course recognize what software requirements are and their importance in successful software project management 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 recognize how functional requirements differ from non-functional requirements describe the importance of requirements management and list the four fundamental requirements management processes describe in detail the requirements management process illustrate through a non-example the shortcomings of traditional requirement specification and management process (ever-changing scope, wasted efforts, demotivated team, etc.) compare the benefits and features of traditional project management against Agile project management identify how the Agile approach helps define and manage software requirements describe the importance of Agile software requirements describe a typical software requirements specification document describe how the feasibility study tool helps determine whether a solution is practically achievable or not summarize the key concepts covered in this course