We've been using Function Point Analysis (FPA) estimation for new software development projects and medium sized changes that involves development efforts for code involving database entities as well (where we plug in EIF, ILF, EI, and EQ information).

However, what are the best estimation methods for:

1. Simple server side scripting changes that don't involve any database components.
2. How does one estimate trivial change requests that have very little code changes, for example UI design, realigning fields, changing error messages, and those sorts of changes.

Even though these changes are trivial, testers have to test it, leads have to review it, manager have to schedule it, and releases need to be planned for pre-production and production deployments.

We've been using Function Point Analysis (FPA) estimation for new software development projects and medium sized changes that involves development efforts for code involving database entities as well (where we plug in EIF, ILF, EI, and EQ information). This process seems to be working out very well for us organization wide.

However, what are the best estimation methods to estimate minor changes such as :

1. Simple server side scripting changes that don't involve any database components.
2. Trivial change requests that have very little code changes, for example UI design, realigning fields, changing error messages, and those sorts of changes.

Even though these changes are trivial, testers have to test it, leads have to review it, manager have to schedule it, and releases need to be planned for pre-production and production deployments.

We've been using Function Point Analysis (FPA) estimation for new software development projects and medium sized changes that involves development efforts for code involving database entities as well (where we plug in EIF, ILF, EI, and EQ information).

However, what are the best suited estimated methods for:

1. Simple server side scripting changes that don't involve any database component.
2. How does one estimate trivial change requests that have very little code changes, for example UI design, realigning fields, changing error messages and those sorts of changes.

Even though these changes are trivial, testers have to test it, leads have to review it, manager have to schedule it, and releases need to be planned for pre-production and production deployments.

We've been using Function Point Analysis (FPA) estimation for new software development projects and medium sized changes that involves development efforts for code involving database entities as well (where we plug in EIF, ILF, EI, and EQ information).

However, what are the best estimation methods for:

1. Simple server side scripting changes that don't involve any database components.
2. How does one estimate trivial change requests that have very little code changes, for example UI design, realigning fields, changing error messages, and those sorts of changes.

Even though these changes are trivial, testers have to test it, leads have to review it, manager have to schedule it, and releases need to be planned for pre-production and production deployments.

So, we've been using FPA estimation for new software development projects and medium sized changes that involves development efforts for code involving database entities as well (where we plug in EIF, ILF, EI, EQ...information).

However, what are the best suited estimated methods for -

1. Simple server side scripting changes that don't involve any database component.
2. How does one estimate trivial change requests that have very little code changes, for example UI design, realigning fields, changing error messages and those sorts of changes.

Even though these changes are trivial, testers have to test it, leads have to review it, manager have to schedules it and releases need to be planned for pre-prod and prod deployments.

Thanks,

Dodz.

We've been using Function Point Analysis (FPA) estimation for new software development projects and medium sized changes that involves development efforts for code involving database entities as well (where we plug in EIF, ILF, EI, and EQ information).

However, what are the best suited estimated methods for:

1. Simple server side scripting changes that don't involve any database component.
2. How does one estimate trivial change requests that have very little code changes, for example UI design, realigning fields, changing error messages and those sorts of changes.

Even though these changes are trivial, testers have to test it, leads have to review it, manager have to schedule it, and releases need to be planned for pre-production and production deployments.