Agile Software Projects: Software Requirements

Agile    |    Beginner
  • 14 videos | 1h 16m 56s
  • Includes Assessment
  • Earns a Badge
  • Certification PMI PDU
Rating 4.4 of 223 users Rating 4.4 of 223 users (223)
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.

WHAT YOU WILL LEARN

  • 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

IN THIS COURSE

  • 1m 32s
    In this video, you’ll learn more about the course and your instructor. In this course, you’ll learn the difference between software requirements, functional requirements, and non-functional requirements. Next, you’ll review the shortcomings of traditional requirements 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. FREE ACCESS
  • 5m 43s
    In this video, you’ll learn more about software requirements. You’ll learn the software development lifecycle has been used for decades to define the general phases of software development. These are the basic phases of the software development lifecycle. Requirements analysis, where client needs are analyzed. Design of the solution, Implementation of Design, Testing of the Design, and the Evolution phase in which the solution goes for another round of updates starting with Requirements. FREE ACCESS
  • Locked
    3.  Functional Requirements
    5m 5s
    In this video, you’ll learn more about the functional requirements of building software. These solid requirements help when building software in the same way a blueprint helps when building a house. Here, you’ll learn that functional requirements define the function of a system or components of a system. They define what the system does. FREE ACCESS
  • Locked
    4.  Non-functional Requirements
    6m 22s
    In this video, you’ll learn more about non-functional requirements that make up a system. These are the behaviors and limitations of the system that are important to users. Where functional requirements define what a system does, non-functional requirements define how it does it. Non-functional requirements speak to the quality of the system from the user's perspective. Non-functional requirements are also referred to as quality attributes or constraints. FREE ACCESS
  • Locked
    5.  Functional and Non-functional Requirements
    7m 16s
    In this video, you’ll learn more about functional and non-functional requirements. You’ll compare and contrast the two. Functional requirements are the features that end-users demand. They're what the system is designed to do. Non-functional requirements represent the quality of the system. These are the quantitative descriptions of quality that must be met via tests. Non-functional requirements are by nature prioritized by the customer. FREE ACCESS
  • Locked
    6.  Requirements Management
    4m 56s
    In this video, you’ll learn more about requirements management. You’ll learn that requirements change, so you have to update them regularly. These activities ensure your requirements are up to date and accurate and reflect the needs of your customers. Requirements management is a set of tasks that manage your requirements so that your needs are fulfilled at the level your customer needs. FREE ACCESS
  • Locked
    7.  Requirements Management Processes
    7m 34s
    In this video, you’ll learn more about the phases of requirements management. Requirements management is a process for ensuring quality requirements throughout a project. Ensuring quality requirements in turn ensures project goals are met. It ensures the solution sufficiently fulfills the customer's needs. FREE ACCESS
  • Locked
    8.  Traditional Requirement Specification Shortcomings
    5m 36s
    In this video, you’ll learn more about traditional requirement specification shortcomings. You’ll learn there are many pitfalls to traditional requirement specification writing. Poor requirement specifications can lead to poor communication among stakeholders, time delays, and extra costs. This can lead to a misaligned final product that doesn't meet the customer's needs. FREE ACCESS
  • Locked
    9.  Traditional Management Process Shortcomings
    6m 43s
    In this video, you’ll learn more about software project management approaches. The two most popular approaches are the Waterfall approach, which is an example of the traditional approach to management, and Agile, which is considered a more modern approach to software development. You’ll learn more about each of these approaches here. FREE ACCESS
  • Locked
    10.  Agile Software Management
    6m 3s
    In this video, you’ll learn more about the Agile Software Management process. Agile is a software development process that's gained a lot of popularity over the last decade. The process has largely superseded more traditional forms of software development such as the Waterfall method. Agile is an iterative process. All the phases of the Agile software development life cycle take place within a single iteration and are repeated multiple times during a project. FREE ACCESS
  • Locked
    11.  Agile Software Requirements
    6m 30s
    In this video, you’ll learn more about Agile Software Requirements, called user stories. User stories in Agile define the capabilities wanted in a system, from the user’s perspective. These are focused on the user experience. They’re a clear picture of what the user wants, not a description of the solution. They answer the questions, who, what, and why? Who wants it, what do they want, and why do they want it? FREE ACCESS
  • Locked
    12.  Software Requirements Specification Document
    7m 32s
    In this video, you’ll learn more about the Software Requirements Specification, or the SRS document. An SRS document has a standardized format. There are different standards, but one common one has been documented by the Institute of Electrical and Electronics Engineers or IEEE. The document explains the functionality of the software or what it does. It describes the external interface, such as the UI, or how external clients will interact with APIs. FREE ACCESS
  • Locked
    13.  Software Feasibility Tool
    5m 13s
    In this video, you’ll learn more about the software feasibility tool. Because software is expensive to develop, companies run a software feasibility study before agreeing to a project. A software feasibility study helps determine the likelihood of a project's success. Feasibility studies are performed prior to the start of project activities. There are many benefits to running a feasibility study. They help you identify the market for your project and ensure the project generates money. FREE ACCESS
  • Locked
    14.  Course Summary
    51s
    In this video, you’ll summarize what you’ve learned in the course. You examined Agile software requirements, their importance, and methods. You’ve explored using functional and non-functional requirements and their differences. You also learned the importance of requirements management and its processes. You discovered the shortcomings of traditional requirements specifications and processes. You also learned about the Agile approach to software management and requirements. Finally, you learned the software requirements specification document and software feasibility tool. FREE ACCESS

EARN A DIGITAL BADGE WHEN YOU COMPLETE THIS COURSE

Skillsoft is providing you the opportunity to earn a digital badge upon successful completion on some of our courses, which can be shared on any social network or business platform.

Digital badges are yours to keep, forever.

YOU MIGHT ALSO LIKE

Rating 3.9 of 20 users Rating 3.9 of 20 users (20)
Rating 4.6 of 16 users Rating 4.6 of 16 users (16)
Rating 4.5 of 17 users Rating 4.5 of 17 users (17)

PEOPLE WHO VIEWED THIS ALSO VIEWED THESE

Rating 4.3 of 131 users Rating 4.3 of 131 users (131)
Rating 4.5 of 39 users Rating 4.5 of 39 users (39)
Rating 4.4 of 20 users Rating 4.4 of 20 users (20)