--Originally published at Memogcia blog

Quality assurance is the most important thing that a project or product has to have. Why? because It’s the trust that your clients will give the product. When we said quality we think that the product need to pass several tests, to achieve quality, but the reality is that quality means the product need to be tested yeah but also needs to have technical reviewing and project planning, all these will bring to us early detection and correction of defects.

--Originally published at Memogcia blog

--Originally published at Memogcia blog

More software projects have gone awry for lack of calendar time than for so all projects have gone awry for lack of calendar time other causes combined. Why  this cause of disaster is common? First, our techniques of estimating are poorly developed. seriously, they reflect true, i.e., that all will an unvoiced assumption which is More quite un- go well. Second, our estimating techniques fallaciously confuse effort with progress, hiding the assumption that men and months are interchangeable. Third, because we are uncertain of our estimates, software managers often lack the courteous stubbornness of Antoine’s chef. Fourth, schedule progress is poorly monitored. Techniques proven and routine in other engineering disciplines are considered radical innovations in software engineering. Fifth, when
schedule slippage is recognized, the natural (and is to add manpower. Like dousing a fire with makes matters worse, much worse. More fire re- more gasoline, and thus begins a regenerative cycle which traditional) response gasoline, this quires ends in disaster.  Schedule monitoring will be the subject of a separate essay. Let us consider other aspects of the problem in more detail.

--Originally published at Memogcia blog

Hi, I’m going to tell you about how to implement “staged delivery” in your software project. First of all let’s discuss what is staged delivery. Staged delivery is an approach to organize the deliveries on a software project, it is based in stages, there isn’t a magic number for this, some one need 5, 2 or just one stage to release the product. Why staged delivery is the best? because this means the most important part of the project is going to be build at the first stages. The best of all is that everybody could track it, upper management, costumers and users.

Software projects are divided into three conceptual stages:

The first phase is going to be discovery, here is where the uncertainty areas changed to certainty areas. Here is where technical investigation and building user interface prototypes take place.

In the middle of the project is where the phase change to invention. Here is where developers at macro level invent a software architecture and design. At the micro level, each function or class may require small inventions.

In last part the phase shifts again into implementation. In this phase is where the work done in discovery and invention are mapped.

The next figure illustrates how a staged delivery take place:

This plan emphasizes project planning and risk reduction. The project team develops a software concept first, then gathers and analyses requirements and then completes an architectural design. In each stage the project team does detailed design, coding, debugging, and testing. As I mentioned at first It doesn’t need to be 3 stages, this is only a example of how it will be if there is only 3 stages. But in real life it will take more than three or less.

The benefits of this are:

• Critical functionality is available earlier.
• Risk are reduced early.
• Problems become evident early.
• Status-reporting overhead is reduced.
• Staged delivery makes more options available.
• Staged delivery reduces the possibility if estimation error.
• Staged delivery balances flexibility and efficiency.

But there are some disadvantages:

• Increases project overhead.
• Retest already tested features.
• Perform version control tasks associated with making a delivery
• Address extra complexity of supporting additional versions of the software in the field.

The next picture define a well structured project and its stages:

The black line shows the nominal code growth pattern, and the shades area shows the range of normal variations. The variations in code growth in the middle of the project are due too interim releases in which the projects emphasis shifts from generating new code to raising the quality of existing code.

Telling this, here is another approach:

Change control procedure

This approach ensure the project to be stable if there are changes ready to be implemented. This approach evaluates, control and approves important changes.

--Originally published at Memogcia blog

When someone is working on a project it is required that the objectives need to be clear and direct. If the software developers know what to do, have talks with their superiors the objectives will be complete more easily.

--Originally published at Memogcia blog