npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

estimate-tasks

v1.0.0

Published

Given the individual tasks' estimations, calculates the total estimation for the whole project

Downloads

11

Readme

Build Status

About

Given the individual tasks' estimations (in hours), calculates the total estimation for the whole project. It attempts to do the right thing, when summing up estimations, treating each individual estimate as a continuous random variable (see Math), and applying a formula from Steve McConnel's book "Software Estimation: Demystifying the Black Art".

Doing the math right though requires providing a range for an individual estimate instead of a single number: you'll be asked for the best case, the most likely case, and the worst case hours.

By the way, the probability of a task taking exactly X hours to finish is exactly zero (see Math again ;).

Also, a subjective confidence factor is provided for each task's estimation, in percent, within the range (0, 100) -- excluding 0 and 100. Normally, you should be pretty confident in the most of your tasks' estimations, specifying confidence factors above 90% for them. Only a smaller part of tasks should have 90% and below. Anyway, that's a just fine tuning mechanism; you may well ignore it, and simply assign, say, 95% confidence to all the tasks.

The number E you get from total75PercentLikelyHours() means that there's a 75% probability that your project will take not more than E hours.

Installation

Node.js:

$ npm install estimate-tasks

Web browser:

$ bower install estimate-tasks

API

Node version:

var et = require("estimate-tasks"),

    total = et.total75PercentLikelyHours([{
        bestCaseHours: 1,
        mostLikelyCaseHours: 1.5,
        worstCaseHours: 4,
        confidencePercent: 99.9
    }, {
        bestCaseHours: 8,
        mostLikelyCaseHours: 10,
        worstCaseHours: 12,
        confidencePercent: 66
    }, {
        bestCaseHours: 2,
        mostLikelyCaseHours: 3,
        worstCaseHours: 4,
        confidencePercent: 95
    }]);

In the browser you have to include the lib/calc.js script. Then:

var et = window["estimate-tasks"];

Testing

Test-driven with Mocha. Under Node, say:

~/estimate-tasks(master)$ npm test