Stateless Code | Populate the Project Backlog with Preliminary Features for the App @StatelessCode | Uploaded August 2023 | Updated October 2024, 29 minutes ago.
We've got our user authentication with Devise working and took care of some housekeeping items and now our backlog has been depleted almost down to nothing. If this were writing a book, we would be staring at a blank page. Where do we begin?
In this video, we take a three phase approach to initial population of the backlog:
Step 1: Brainstorm a list of features and get them into the backlog. Order, priority, feasibility and value beyond it being a potential wish list item don't really matter.
Step 2: Rearrange the backlog by value, ignoring execution order and dependencies.
Step 3: Rearrange the backlog again, taking into account execution order and dependencies.
This is still early in the project's lifecycle. There are a lot of unknowns, but one thing you can take to the bank is that we won't just execute through the backlog in the order it is in by the end of this video without making modifications. As we work through the backlog, ideas for improvement and iteration will come up as we iterate on the application. We will learn things and flesh things out more. Thankfully the Ruby on Rails framework is among the best available for adapting to these changes when we do need to pivot.
This video covers:
00:00:00 Introduction, review recent videos and backlog
00:02:18 Overview of a project backlog and plan for the video
00:05:22 Review initial "brainstorm" version of the backlog
00:09:19 Rearrange and review the "abolute order" version of the backlog
00:14:27 Rearrange backlog to a more realistic "execution order"
00:16:09 Example of how a lower priority item might influence a design decision
00:19:26 Anticipating change and adaptability to backlog changes
#ruby #rails7 #rails #rubyonrails #rubygems #codecast #screencast #github #opensource #minitest #TDD #agile #NerdDice #DnD #roleplaying #softwaredevelopment #learntocode #tailwind #postgresql #rubocop #devise #turbo #controllers #views #selenium #capybara #systemtest #agile #backlog
See other related StatelessCode videos:
- Exploring My Table Top Role-Playing User Persona youtu.be/k5c6oE6uoGc
- Why Rails in the 2020s? youtu.be/f1ca3rKQSD0
This video is CC0 - No rights reserved. (YouTube doesn't allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of "intellectual property". Copying is not stealing.
We've got our user authentication with Devise working and took care of some housekeeping items and now our backlog has been depleted almost down to nothing. If this were writing a book, we would be staring at a blank page. Where do we begin?
In this video, we take a three phase approach to initial population of the backlog:
Step 1: Brainstorm a list of features and get them into the backlog. Order, priority, feasibility and value beyond it being a potential wish list item don't really matter.
Step 2: Rearrange the backlog by value, ignoring execution order and dependencies.
Step 3: Rearrange the backlog again, taking into account execution order and dependencies.
This is still early in the project's lifecycle. There are a lot of unknowns, but one thing you can take to the bank is that we won't just execute through the backlog in the order it is in by the end of this video without making modifications. As we work through the backlog, ideas for improvement and iteration will come up as we iterate on the application. We will learn things and flesh things out more. Thankfully the Ruby on Rails framework is among the best available for adapting to these changes when we do need to pivot.
This video covers:
00:00:00 Introduction, review recent videos and backlog
00:02:18 Overview of a project backlog and plan for the video
00:05:22 Review initial "brainstorm" version of the backlog
00:09:19 Rearrange and review the "abolute order" version of the backlog
00:14:27 Rearrange backlog to a more realistic "execution order"
00:16:09 Example of how a lower priority item might influence a design decision
00:19:26 Anticipating change and adaptability to backlog changes
#ruby #rails7 #rails #rubyonrails #rubygems #codecast #screencast #github #opensource #minitest #TDD #agile #NerdDice #DnD #roleplaying #softwaredevelopment #learntocode #tailwind #postgresql #rubocop #devise #turbo #controllers #views #selenium #capybara #systemtest #agile #backlog
See other related StatelessCode videos:
- Exploring My Table Top Role-Playing User Persona youtu.be/k5c6oE6uoGc
- Why Rails in the 2020s? youtu.be/f1ca3rKQSD0
This video is CC0 - No rights reserved. (YouTube doesn't allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of "intellectual property". Copying is not stealing.
