About This Chapter
Agile & Scrum Software Development - Chapter Summary
With this chapter's lessons, your employees will have an efficient way to improve their knowledge of documentation in using Agile & Scrum software and the transparency of the systems. Have them follow along with these lessons to improve their understanding of:
- Agile and Scrum documentation
- Agile and Scrum epics
- User stories and how to create them with Agile
- Managing Agile and Scrum backlogs
- Agile estimations and planning
- Velocity in Scrum and Agile
Following these short, engaging lessons, employees may complete self-assessment quizzes that will help them identify topics they may want to review further. Once they have completed all the lessons and quizzes of the chapter, employees can also take the practice chapter exam for an additional assessment of their knowledge.
How It Helps
- Improves skills: After this chapter, employees should possess a better working knowledge of Agile & Scrum artifacts and transparency.
- Creates security : Knowing how artifacts are stored and the transparency of the artifacts will help build more secure systems.
- Improves efficiency: With a better understanding of Agile & Scrum artifacts and transparency, systems can be used more efficiently.
By the end of this chapter, employees will be able to:
- Understand Agile and Scrum documentation
- Create Agile and Scrum epics and user stories
- Manage Agile and Scrum backlogs
- Plan and make estimations with Agile and Scrum
1. Agile Documentation: Methodology, Requirements & Examples
Agile seeks an alternative to an overemphasis on documentation by traditional project methodologies, but it still places some value on documentation. Learn about Agile documentation, including its methodology and requirements, and see examples.
2. Scrum Documentation: Process & Example
Scrum is an alternative to the different aspects of traditional project methodology, including extensive documentation. Rather than a lack of documentation, the goal is to document only what is necessary. Learn the process of Scrum documentation in this lesson.
3. Epic in Agile: Definition & Example
Project requirements are often defined over time, rather than all at once. In Agile, epics can be used as a placeholder for requirements that need further definition. Learn about epics in Agile.
4. Scrum Epic: Definition & Examples
Project work in Scrum is only taken on if it is in the form of a user story. Despite this, work items can take other forms, such as epics, that must be turned into user stories. Learn the definition and understand examples of Scrum epics.
5. Sprints in Agile & Scrum: Definition & Methodology
One goal of Agile and Scrum is to produce tangible results and receive feedback as early as possible. This cannot be accomplished through an extended, linear timeline but requires a breakdown into short, repeated sprints. Learn the definition and methodology of sprints in Agile and Scrum.
6. Agile User Stories: Definition & Format
While there are different methodologies used to implement Agile, the treatment of project work is the same in each. Agile project work is consistently broken down into user story form. Learn the definition and format of Agile user stories.
7. How to Write an Agile User Story
One of the most important factors in project success is the quality of the requirements. In Agile, project requirements take the form of user stories. In this lesson you will learn what an Agile user story is and how to write one.
8. Agile Story Mapping: Tools & Examples
The lesson describes how to use Agile Story Mapping in Software Development Process which is used to organize user stories. User stories are high level requirements in non technical language and ordering them according to several factors helps in creating a roadmap .
9. Best Practices for Writing Agile User Stories
One of the factors that dictate success for a project is the quality of project requirements. In Agile, project requirements take the form of user stories. Learn the best practices for writing quality user stories.
10. INVEST Mnemonic in Scrum User Stories
The INVEST mnemonic provides a set of guidelines to help Scrum team members write better user stories. Learn what the mnemonic means and how to apply it.
11. Agile Acceptance Criteria
The value of a project is determined by its completion and whether or not the results satisfy the project objectives. In Agile, acceptance criteria are used to determine if a project has been completed as requested. In this lesson, we will learn about Agile acceptance criteria and how they are applied in judging a project's success.
12. Definition of Done in Agile
In agile software development, developers use the definition of done to determine when a project is truly complete. Learn how you can come up with a definition of done that is appropriate for your team and customers.
13. Agile Backlog: Definition & Management
Project requirements are most valuable when they are easy to understand and implement. In Agile, management of project requirements is done through the use of a backlog. Learn the definition and management of an Agile backlog.
14. Agile Backlog: Grooming & Prioritization
Project requirements in Agile are broken down into more manageable forms and kept in a backlog. This approach allows for more flexibility for the order in which requirements are completed. Learn about Agile backlogs and how they are groomed and prioritized.
15. Scrum Sprint Backlog: Main Purpose & Example
In a Scrum project, requirements are continually broken down in order to be more manageable. This occurs when they are created, as well as when they are taken into the sprint backlog. Learn the main purpose of a Scrum sprint backlog.
16. Agile Product Backlog vs. Sprint Backlog
This lesson explains the main differences between a product backlog and a sprint backlog in agile software development, how each of those backlogs is used, and the responsibilities that the customers and developers have in relation to those backlogs.
17. Scrum Board: Definition & Examples
Scrum is a transparent process where the current state of a project is readily available. This transparency comes through the use of Scrum boards. Understand the definition of a Scrum board and see some examples.
18. Estimating Agile Story Points
Each task in a project involves a varying combination of time and effort to complete. Agile attempts to quantify this combination using story points. Learn about estimating Agile story points.
19. Agile Estimating & Planning
Estimating and planning activities in Agile project management are handled using an incremental process, rather than occurring at the very start of a project. In this lesson, we explore how this actually occurs over time.
20. Agile Estimation: Units & Techniques
Project requirements are one of the most important aspects of a project, but the time and effort are of equal significance. In Agile, time and effort are assigned using estimation. Learn about the units and techniques of Agile estimation.
21. Agile Poker: Planning Through Cards
Planning poker is an estimation technique used in the scrum framework. It is meant to clarify how complex user stories are and ensures the team isn't being over-committed.
22. Timebox in Scrum & Agile Management
Look! It's a bird! No, it's a plane! No, it's a timebox! Ever hear this word and wonder what it meant? Explore this lesson, and you will learn about timeboxing, an important, valuable practice of Agile.
23. Scrum Velocity: Definition & Calculation
The main questions for a project are when and how efficiently it will be completed. In most project methodologies, there are numerous calculations and measurements to answer these questions. In Scrum, only velocity is needed to provide the answers.
24. Velocity in Agile: Definition & Formula
When working on projects, measurements of past performance can help lead to future success. One of the key metrics of performance in Agile is velocity. Learn the definition and formula for velocity in Agile.
25. Sprint Burndown Chart in Scrum: Example & Overview
Every project management method needs a tool for monitoring performance. One of the most popular tools for monitoring project progress and tracking team performance in Scrum is a burndown chart. Explore the Sprint Burndown Chart to learn how work is tracked in Scrum.
26. Release Burndown Chart in Scrum: Example & Overview
Will the project team be ready to release the product to the customer in time? Learn to track the progress of a Scrum development team towards a product release with the release burndown chart.
27. Risk Burndown Chart: Example & Overview
This lesson will discuss the need for a risk burn down chart. It will also show a step by step process for creating a risk burn down chart that can be used for risk management.
28. Burn Up Chart vs Burndown Chart in Scrum
Should you burn it up or burn it down? Both if you want! If you think these are names for the latest dance moves, you're wrong. They are charts used in the Scrum software development framework. After this lesson, you will understand what they are and how to create them.
29. The Agile Release Planning Process
While Agile development relies on planning iteratively at the team level, most software organizations require a higher level of release planning for large releases. In this lesson we explore the basic concepts behind the release planning process.
Earning College Credit
Did you know… We have over 200 college courses that prepare you to earn credit by exam that is accepted by over 1,500 colleges and universities. You can test out of the first two years of college and save thousands off your degree. Anyone can earn credit-by-exam regardless of age or education level.
To learn more, visit our Earning Credit Page
Transferring credit to the school of your choice
Not sure what college you want to attend yet? Study.com has thousands of articles about every imaginable degree, area of study and career path that can help you find the school that's right for you.
Other chapters within the Agile & Scrum Training course