this post was submitted on 20 Dec 2023
22 points (92.3% liked)

Programming

17668 readers
200 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
22
Freelancing (?) programmers here: How do you estimate how many scrum points a specific project will require? Is there a template? (self.programming)
submitted 1 year ago by erayerdin to c/programming
5 comments fedilink hide all child comments
 

I know this is kind of a soft problem and is highly dependent on the context of a project.

For my own projects, I use scrum points to estimate how much effort it will require to reach to a certain point. I measured my throughput and it seems like, with the amount of time left from my daily job, I can complete around 100 points every month.

Recently, this idea is stuck in my head. Every (web/mobile) project requires a certain set of requirements such as:

  • Authentication and authorization
  • Performance metrics and logging
  • Storage
  • CRUD for each model etc.

Of course, mostly through Firebase.

I was wondering if there's a way, a website or a platform maybe, to define a list of features/stories and get an estimated total points.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 1 year ago

As a Scrum Master myself this isn't a question anyone outside of your work flow can answer. I've worked at organizations where we expected people to complete 8 points of work per sprint, and some where we expected people to do 30. Additionally, from a pure philosophy stand point, points measure complexity/uncertainty not time needed to complete the task. As such, you should be both reducing the average number of points per feature and increasing your average velocity over time.

OK, semantics aside, here's some useful advice: jira has free accounts for individuals (check with their licenses before you sell any work) and is obviously built for software development. You can also install addons like Clone Plus that will let you clone epics and the stories within them. I'd recommend making a shell epic that contains the maximum amount of work a project would take, then appropriately size, sequence, and relate all stories to each other. After you have that template epic you can clone it and all the relevant stories underneath, then using Jira dashboards put them in the order they need to be done and use your estimated weekly velocity to see what you can do. Then you'll have a list of tasks, how many points they total, and a rough timeline of story delivery