Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/slashsbin/styleguide-agile
/sBin/StyleGuide/Agile
https://github.com/slashsbin/styleguide-agile
agile code-review codereview fibonacci-numbers storypoint style-guide styleguide
Last synced: 24 days ago
JSON representation
/sBin/StyleGuide/Agile
- Host: GitHub
- URL: https://github.com/slashsbin/styleguide-agile
- Owner: slashsbin
- Created: 2016-06-24T10:35:50.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2024-04-18T06:25:34.000Z (10 months ago)
- Last Synced: 2024-11-14T12:14:28.980Z (3 months ago)
- Topics: agile, code-review, codereview, fibonacci-numbers, storypoint, style-guide, styleguide
- Language: HTML
- Homepage: http://slashsbin.dev/styleguide-agile/
- Size: 5.86 KB
- Stars: 5
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Agile
## Story Points
### Steps/Levels
Ten Levels:
> 1 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > 10
### Fibonacci Numbers
```
F(n) = F(n-1) + F(n-2)
Seed:
F0 = 0
F1 = 1
```
Points are based on [Fibonacci Numbers](https://en.wikipedia.org/wiki/Fibonacci_number):
> 1 > 3 > 5 > 8 > 13 > 21 > 34 > 55 > 89 > 144
- Numbers `1`, `2` were removed from Original Sequence:
- `F(2)`: Additional Number `1` were Removed due to Conflicting with 1st Step(Aka `F(1)`)
- `F(3)`: Number `2` were Removed due to Closeness to Siblings
- It's a [Complete Sequence](https://en.wikipedia.org/wiki/Complete_sequence) which means Points can be Merged Disgustingly to Construct New Points.
- Has Same Natural Meaning for Complexity Increase of Points for Tasks: Each subsequent number is the sum of the previous two, which Means every Task with Higher Point is Complex as Two Tasks with Previous Points!
### Choose Points: How hard is to Implement a Task?
* Included Factors:
1. *Complexity*
2. *Unknowns*
3. *Effort*
* Non-Included Factors:
1. *Time*
2. *Assignee*
### Ground Rules
- `F(6)`: Number `8` is the Common/Middle Point:
- Everyone in a [Cross-Functional](https://en.wikipedia.org/wiki/Cross-functional_team) Team can Do this!
- Other Tasks Points are Calculated Compared to this Point.
* * *
## Code Review
### Checklist
- Code
- [ ] Does it Compile?
- [ ] Can you spot any runtime errors just by looking at code?
- [ ] Is the feature/bugfix complete?
- [ ] Is this a good solution?
- [ ] Does it introduce any security holes?
- [ ] Is the code efficent?
- [ ] Is it logically correct?
- [ ] How does it affect the rest of the system?
- [ ] Is it within scope?
- [ ] Are there any code style issues?
- [ ] Is the code readable?
- [ ] Does it have good and enough documentation?
- Automated testing
- [ ] Does it need tests?
- [ ] Does it have tests?
- [ ] Are tests logically correct?
- [ ] Are tests simple, easy to read and debug?
- [ ] Are tests testing the right thing?
- [ ] Are tests testing the edge cases?
- Manual testing
- [ ] Can you run the code?
- [ ] Can you follow through several test scenarios?
- [ ] Is the rest of the system looking/working fine?
- [ ] Can you break it?
##### References
- https://ana-balica.github.io/2017/02/21/code-review-checklist/