#software estimation

Do you know that over 66% of projects overrun costs? In this video, we’ll describe a software estimation process that helps to avoid overspending.

Why Do We Need Software Estimation? Estimates provide value to both clients and providers. So, clients get information about the time required to complete the project and the approximate project budget.

The software development estimation process consists of multiple activities that include estimating the timeline, cost, models to be used, testing period etc. In simple terms, Software development estimation will determine how long and how much does the project cost for the client. Software estimation process is one of the hardest and plays vital role in the sales/acquisition process. Couple of days headache for a project manager to come up with the same. In some cases, it takes more than that as it involves detailed review of the requirement and discussion between the both parties.

Companies have to consider some steps which will help for an estimation process.

Understand the requirement if it is already available as off-the-shelf solution and suggest the customer for the same.

The identified off-the-shelf solution benefits need to explain to the customer and how customisation happens and to what extend it is possible.

Identify the theme which can be used and put some Business Analysis in estimate for further review of the theme and choosing the best solution.

Get the timeline and allotted budget of the project to be delivered from the customer if they have in mind.

Consider an architecture which helps for a long run of the business. Try to convince the customer the benefits of going for a best architecture in terms of database if it really helps them.

Be clear with the features that you do not have the certainty and clarify with the client if any chance.

Take in account the buffer hours required for the entire development process. Based on the complexity, 20-40 hours are suggested.

Consider the resources experience level to be deployed in the project as it also affects in the timeline of the project.

Understanding the requirement will take some extra time and consider more hours for the first week to get a grip on the project.

If the customer is non-technical, explain the support cost, hosting, AMC (Annual maintenance cost) etc in the proposal/estimate.

Address the software development life-cycle to the customer along with sharing estimate.

How CronJ makes it accurate with some smart moves:

Prepare the questions with respect to the requirement in the initial call itself. This makes customers more comfortable to explain the requirement better rather than simply presenting the organisation’s deck. In all our normal inbound inquiries, there is a message body which fills by the customer with 1-2 line requirement.

Analyse the past projects and check the similarity of features and how we implemented.

Segregation of all the proposals/estimates where you can relate any new requirement.

Reuse the modules which is already used in the previous estimates.

Discussions with the senior team members before finalising the estimate to client.

Research as much as we can. Always commit 2+ days to come up with an estimate.

Revise the estimate couple of times and finalise it with the approval of Chief Technical Officer.

Above to all, we are transparent to the customer and add the comments in the same excel sheet/proposal that we submit to client explaining the uncertainties and risks.

The estimation process will get improved over time and easier once you got into the process of estimation. Following the best practices for estimation also help in this stage. Providing the flexible engagement models, CronJ is able to make a good move and satisfy the customer once they start a discussion with us.

Officiate Reset Analysis (FPA) is a sizing accent mark of clear business significance. First extracted public by Allan Albrecht as to IBM in 1979, the FPA technique quantifies the functions contained within software entree terms that are meaningful to the software users. The dkl relates summarily to the business requirements that the software is intended to artfulness. Self can thuswise be readily applied across a wide margin of development environments and to the brim the life of a pullulation forecast, exception taken of early requirements definition to full inaction use. Other business measures, such as the productivity of the development step and the cost per unit to jockstrap the software, parcel also be readily derived.The FP measure itself is derived harmony a number regarding stages. Using a standardized set of aboriginal criteria, each of the business functions is a numeric minimus according to its type and complexity. These indices are totaled to give an undersign measure of size which is ancient normalized by incorporating a number as regards factors relating to the software as a whole. The end result is a any one grain called the FP table of contents which measures the size and complexity respecting the software product.<\p>

Vestibule summary, the FP technique provides an end in view, comparative measure that assists in the evaluation, planning, management and control of software production.<\p>

FPA measures functional requirements in terms of the business transactions functions that the user chamber pot perform using the software, and the business postulate (collections of data that the software battlewagon store and ingroup). PMP s: This course counts for 8 Professional Grooming Units (PDU's). The process in relation to gag FPA is called a 'FP Count' and it involves the categorization, classification and weighting of transactions and data elements. Weighted values are combined on route to yield the functional size. Good terms IFPUG methodology, the prey result is referred to as the Adjusted Syntactic analysis Point Measure. The methodology is maintained by the International Function Point Users Group (IFPUG). FPA quantifies the functionality delivered over against the user based eventuating expressed requirements - the "logical" view of size as opposed on the physical or technical view. The FPA technique is used to assess the functionality delivered by software and a 'function point' is the unit of largeness. The workshop provides participants with an enhanced understanding of: Function Pertinence (FP) Counting Guidelines, hints, and examples so understand FP Measurement Italic drill on use of FP in software apotheosis Use and limitation of Operations Point dexterousness.<\p>

Software Estimation – part 2 of 2

A summary, some tips & tricks, after reading a book called “Software Estimation – Demystifying the “Black Art”. …

Story Points: How I Learned to Stop Worrying and Love Software Estimation

Everyone who has used Scrum knows what user stories are. Most people who have used Scrum know what story points are. Few people who have used Scrum really get the idea behind story points. It’s not too surprising. The concept doesn’t always fit well into the ultra left-brained, concrete mindset of most software developers commonly found in the wild. The problem is that developers over-think story points because they don’t fully understand the context in which they are being used. I’m going to talk a little bit about how story points work and why we need to stop thinking so hard about them.

You probably don’t estimate software projects very well. No, not you. I mean my other reader. You, of course do it fine. But the other person reading most likely doesn’t do it very well at all. Estimating software is a rather complex task, after all. You can’t be expected to get it right all the time.

  Besides, isn’t it a truism that you can’t really know how long a thing is going to take until after you do it? How come management doesn’t understand that? Why can’t they just tell you what to build and then give you all the time you want to build it? Why do they keep changing their minds? How come they ask you to estimate fifty different things, but then only actually choose to do one of them?

They must be a very indecisive bunch indeed! No doubt you would be much better at their jobs than they are. After all, the last time they wrote software it was called COBOL and done on something called a minicomputer – which you looked up on Wikipedia once and, despite the name, was fucking huge!

Those dinosaurs in management, they’ve probably never even heard of the Wu Tang Clan. Yet they tell you to estimate these incredibly complicated web pages they want you to build and then have the gall to hold you to the estimate at the end of the project! Obviously they are completely clueless. What do they think programming is, a science?

Also, at the end of the last project, there were all these things that needed to get done and those idiots didn’t even know that they should have planned for them. I mean, how come it isn’t obvious to them that they should have added extra time to the project for creating an installer, and upgrading the existing database, and writing the release documentation, and testing the flash launcher for the autorun on the CD? And for that matter, when you told them that you had only planned for one hundred simultaneous users and they wanted to put ten thousand on it, why didn’t they automatically increase the time allotted?

It’s a good thing I created this toolto help them plan software projects. Couldn’t have come a moment too soon. Really, I’m just saving them from themselves, that’s all I’m doing.

Though, when you use it, make sure not to estimate anything too big. Don’t put a task on the list that is more than a couple days. I know, in your head, you’ve no doubt already thought through all the steps involved in the month long task and you should be able to put month long tasks on there if you want. And truly, I’m not going to stop you from measuring time in months if you like. Or years, even. Surely you are so brilliant you could just put down a single number for the entire project and be done with it.

But like that filthy calculus teacher you had in university who you are sure was bumping uglies with the blonde from the second and first row (parts of her extended into the seat in front of her, you see), the bastard managers want you to show your work. So show your work! After all you’ve already thought it through, may as well type it up. Put only day long tasks on the list. Couple days at most. Divide a day in quarters even. Really give them what for! Make them have to read. They’ll see how valuable you are then!