agaric/documentation
10
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Compare commits

base: agaric:e1cab6ac1a6c71483ff337a112a5837384a45f82
Branches Tags
agaric:main
agaric:wolcen-main-patch-08376
..
compare: agaric:3e03f5dbc6acbd2dc97253f1c71d4808cd5b19a6
Branches Tags
agaric:main
agaric:wolcen-main-patch-08376

2 commits
e1cab6ac1a ... 3e03f5dbc6

Author SHA1 Message Date
benjamin melançon
3e03f5dbc6 Add stub page for user stories simply to see if links work 2025-07-11 14:59:07 -04:00
benjamin melançon
41d3fdd834 Improve clarity / formatting of stub estimates page 2025-07-11 14:45:11 -04:00
2 changed files with 9 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

9
approach/estimates.md
View file

@ -1,12 +1,15 @@
# Estimates
We write [user stories](approach/user-stories.md) with the client and then estimate complexity on our own, ideally two different developers independently come up with an estimate and then compare and discuss the reason for differences to get to a final number. We write [user stories](approach/user-stories.md) with the client and then estimate complexity on our own, ideally two different developers independently come up with an estimate and then compare and discuss the reason for differences to get to a final number.
We estimate complexity using the Fibonacci sequence because complexity grows exponentially. More info at http://www.yakyma.com/2012/05/why-progressive-estimation-scale-is-so.html We estimate complexity using the Fibonacci sequence because complexity grows exponentially. More info at [yakyma.com/2012/05/why-progressive-estimation-scale-is-so.html](http://www.yakyma.com/2012/05/why-progressive-estimation-scale-is-so.html)
We usually translate that complexity point into twice as many hours. For example, an issue with a complexity of 5 translates to 10 hours. This is based very roughly on our typical velocity. We usually translate that complexity point into twice as many hours. For example, an issue with a complexity of 5 translates to 10 hours. This is based very roughly on our typical velocity.
## Estimating migrations ## Estimating migrations
Historically, We estimate the complexity for migrating Drupal entities roughly based on the following formula: Historically, we get a rough first pass at an estimate of the complexity for migrating Drupal entities based on the following formula:
1 * # Entities + 2 * # Fields = Migration Complexity ```
$number_of_entities + (2 * $number_of_fields) = Migration Complexity
```

3
approach/user-stories.md Normal file
View file

@ -0,0 +1,3 @@
# User stories
We structure most of our development work around *user stories*