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

Programming

17313 readers
357 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 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
22
Freelancing (?) programmers here: How do you estimate how many scrum points a specific project will require? Is there a template? (programming.dev)
submitted 10 months ago by [email protected] to c/[email protected]
4 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
[–] solrize 4 points 10 months ago* (last edited 10 months ago)

I've been at a bunch of companies that use those processes and at best they are like weather forecasting. You can figure out what season you are in, and you can predict the activity of the next few days, but beyond that they are imprecise to the point of uselessness. For freelancing you mostly have to have done such projects all-up already, so you know what you are getting into; and have an idea of what code is out there that you can re-use in your project.

Expect to take horrible beatings on schedules multiple times. And be willing to turn away proposals if you're not comfortable with the timeframes and other issues. As a solo provider there is a limit to how much uncertainty you can absorb.