Scrum helps teams deliver products in an incremental way. Its split up into sprints, which should be less than a month long, where the team works on specific goals. The scrum team always tries to improve their procedures and adapts to new challenges.
Who is in a Scrum Team?
A scrum team is responsible for pretty much all work is required to delivered a product and generally should have less than 10 people.
Product Owner
The product owner tries to create value in the product for stakeholders:
creating and ordering task backlogs
representing the needs of the customer
makes decisions
Scrum Master
The Scrum master helps by:
empowering developers to be self-managed
break down blockers that are in front of the team
establish goals for the product the team is making
in general, helping the team become more effective
Developers
Developers work on the product and also:
create a plan for the sprint
producing quality work
self-managing to acheive sprint goals
Scrum Events
Sprints
During sprints, nothing should be changed to endanger the sprint goal, but the scope can be renegotiated with the scrum master if more information is learned. Each sprint should be between 1-4 weeks long and end with working software.
Theres two goals:
Product Goal: What the product ideally should look like.
Spring Goal: What are we doing this sprint to acheive the product goal?
Core Components of Sprint Planning
Product Owner should make sure that developers are prepared to discuss the backlog
How will this sprint help us acheive our Product Goal?
What can we do this sprint and what is the definition of a task done?
How should a specific task get done?
Sprint Review/Retro
The team should:
Talk about what items are done and not done
Discuss what went well/what could’ve been improved
Discuss how the backlog is looking and if theres any changes to product timelines or priorities
Team can then use that information to plan for the next sprint
I did some searching around and couldn’t find a good introduction that got you set up quickly with a blog and also had it look pretty. I finally found the helpful tutorial here on how to set up the Hyde theme and decided that I will add some helpful hints.
Downloading Ruby
Windows
Go here and find your desired Ruby version.
If you don’t know what system type you have, search up ‘System Information’ in your start menu search bar and look under ‘System Summary’ and ‘System Type’.
P.S. I did end up downlading the ruby with the dev kit.
MacOS
At first I wanted to run this on MacOS because Ruby is included in the system already. This proved to be difficult and I couldn’t figure it out. Because Ruby is preinstalled, Mac doesn’t allow you to edit those Ruby files. It is also heavily discouraged to use sudo to override the safe guards.
I ended up trying this suggestion to no avail. I also ran into homebrew issues which a brew update-reset fixed.
Search for ‘environment variable’ on the start menu
Select ‘Edit the system environment variables’
Click ‘Environment Variables’ at the bottom
Click on the ‘Path’ entry
Using the ‘New’ button, add two entries, one for each Git path listed above
Downloading VSCode
You are more than welcome to use your text editor of choice.
I downloaded VSCode. I did find a peculiar issue: when I download a new package, in order for my terminal to refresh, closing a window and reopening a window wasn’t enough. I had to close VSCode as a whole and then reopen it.
Install Jekyll
gem install jekyll
Install Dependencies
Needed for Poole, which is what Hyde is built on:
gem install jekyll jekyll-gist jekyll-sitemap jekyll-seo-tag
Needed for Hyde:
gem install jekyll-paginate jekyll-gist redcarpet