The first objective of a Software Factory is known to be engaged. The simple answer is immediate, to develop SW but evidently not so simple.
Depending on the type of SW, Technologies and Methodologies chosen must generate the business model.The business model must meet three "simple" questions:
What we sell?
This question tends to answer any MBA reached a "Software Factory", is very clear sell hours, do not sell products. I agree, if SW does not sell products that we sell n times. In this case we can not charge a customer the total number of hours but make a number of sales to recoup the costs. But that's another story.
In this article we will talk to a model of "Software Factory" as one that provides a service related to the SW that isTarifica in hours hours with a price attached.
The first mistake to make, is trying to sell the model as a bodyshopping, on which we do not have any responsibility.Well, it may be the case but then come the JP has direct customer, because what will happen is they will not be satisfied with what they do, and eventually ends up contributing to the JP, systems and people not dimensioned and all for free.The bodyshopping is what it is, if we do it right.
Let's see the models of "Software Factory" that we have, obviously are compatible with each other, but we must differentiate, to know what our sales target and our asking price.
A. Project Development.
In this model the "Software Factory" is in charge of making a concrete development, independent of other applications usually can be based on architectures of the client or themselves.
In the classical model of Project Development, the client makes the functional specification (analysis) and "Software Factory" all the technological development of the project, working with the client in the validation phase.
Points to close in the release process / transition to the customer at the operational level:
Key points to close at the process launch / transition with the client at the level of engineering:
The proper closure or agreement on the above points and channels minimizes risks to the success, the uncertainty about the profit or loss 0.
Obviously there are the other common tasks (Planning, Risk, Staffing, etc) but the part of the project and the above are preliminary.
Based on the above points and the forecast we have about the same with the previous study we calculate the cost estimates, in terms of human resources (number and profile needed), HW resources and additional costs (travel, cost of launch Training) etc. After this calculation we apply the% profit we want to achieve for the project.
Considerations:
- A project of this type can be framed within other broader relationship models have been purchased by a customer.
- The typical technologies in this model that we are, Java and MS .net.
- Are most at risk projects at general maintenance and should be marked% higher profit forecast or a higher cost overruns.
- Each project is different from before, there is no significant productivity gains in the groups of resources allocated to them.
- The% of seniors is higher than maintenance projects. They are therefore more costly projects.
In future articles we'll talk about Maintenance (AM), BPO's, Bodyshoping, Test Factory `s any more ..
Friday, November 19, 2010
Labels: software Factory 0 comments
Subscribe to:
Posts (Atom)
