https://www.amazon.com/dp/B0BQHGLH9F/
The notion of this book started by keeping core and key notes and organizing them in a manila folder. With subject matter encompassing various business techniques and scenarios on what worked and made proper sense at that time, all while keeping an Agile Scrum mindset.
Thus, the ideas and thoughts have been organized into proper categories so one can utilize them to enhance an appetite for knowledge. After each topic, a real working life thought or scenario that was encountered relevant to that topic is told.
Product Backlog and Operating Procedures
1) Before Starting A Project
2) Scrum Master Role Explained
3) Use Deep Method
4) Story Writing
5) Acceptance Criteria (Confirmation)
6) Standard Operating Procedures
7) Application Requirements Guide for Fact Gathering
8) For Growth
Sprint Planning
9) Sprint Planning Format
10) Estimate When Work Will Be Done
11) Estimate A Project
12) Task Board of Work
13) The 4 Nevers
14) Eleven Steps to Problem Solving
Sprint Backlog
15) Sprint Backlog Should
16) Estimation of Story Work
17) Common Estimation Units
18) 4 Core Software Development Project Phases
Daily Scrum
19) Communication Preferences
20) Praise
Product Increment
21) Problem Solving
22) Concerning Guiding Topics
23) Project Management – Best Practices
24) User Story Mapping
Release
25) Definition of Done
26) Continuous Improvement
27) Product Roadmap – Planning
28) Five Phases for Vision
29) Simple Financial Report
30) Keeping Projects – On Time & Within Budget
Sprint Review
31) STAR Methodology (Stage Action Roles)
Sprint Retrospective
32) Retrospective Meeting Agenda
33) Sprint Review Metrics
34) The 5 What's
35) Individual/Team Development
