Detailed Plan

--Originally published at TI2011 – Project Evaluation and Management

Chapter Thirteen – Software Project Survival Guide by Steve McConell

It is important to make a detailed design and it is what this chapter talks about. A detailed design can affect the project. It uses a staged approach, at each stage the developers design milestones that will be delivered at the end of each one. So, having a good architecture will help us to focus and get the plan for the current stage that we are working for.

Also in this stage is when developers check and reuse components and code for others projects, sometimes it could happen that when you reuse a lot of components you make this into a library that you can use for any project that will need those.

Every detail is important during this stage, because the requirements must be clear, if not it must be resilved during another stage but it should be informed about this delay (that is a bad idea). You must consider that developers must continue doing detailed design until they get milestone for the construction.

If many persons know each part of the project with the detailed design, then you will have at least another plan to continue with the project.

Resultado de imagen para flow project toon

Finally, if you make a perfect detailed design, but no one cannot read it, then you’re doing something wrong. Be sure to use detailed design on your projects, it will help to deliver your project during the delopment process.

 


Almost done? – Final preparations

--Originally published at TI2011 – Project Evaluation and Management

Chapter Eleven – Software Project Survival Guide by Steve McConell

Resultado de imagen para almost done

Once we know the important things about how we are going to plan, design, avoid and develop our proyect then we are ready for final preparations.

The developers team is ready to create its first estimates, develop plans for deliverys and get a solid organization on the project.

So, lets talk about create meaningful estimates, because it is posible that the team can give its own estimates, but they must know that the estimates must contain effort, cost, and shcedule, should be written, assuming that the team will not work overtime, it should be created over estimation software, should be based on previous projects. All of this must have a lot of organization because estimates can change everytime.

Keep in mind risks in every stage and estimate in the project. Write a Staged Delivery Plan, deivering in stages with functionalities.

It is important that everything (risks, changes, bugs) can happen on a project, so the project estimation is necessary and important because is the way to know what you will deliver and do, and always try to see if the estimate will be reachable in order to say yes or no for the develoment.

 

 


Es consistente mi PROYECTO?

--Originally published at TI2011 – Project Evaluation and Management

Como saber si nuestro proyecto, requerimientos, diseños, entre otros son adecuados, consistentes y bien diseñados, quizás no lo son y podríamos afectar todo el desarrollo del proyecto en si.

Recientemente en un proyecto en el que estoy trabajando actualmente, se definieron 20 brechas o requerimientos para todo el desarrollo del proyecto. Pero ¿en realidad son suficientes para el diseño, planeación y desarrollo de tal? Realmente me cuestione esto, y dentro de unas de mis conclusiones fue, depende el tamaño del proyecto, porque si es un proyecto que en realidad solo va a tomar a lo mucho un mes quizás eran las adecuadas, pero luego vino otra cuestión en realidad el proyecto esta contemplado para desarrollarse en tres – cuatro meses a lo mucho, entonces es ahí cuando realmente surgió el problema, no estaba bien definido el proyecto, lo que se iba a realizar no solo era un simple proyecto, sino un desarrollo para una empresa, el cual sus transacciones y operaciones de la misma dependían del mismo desarrollo de este proyecto.

Entonces ¿cuál es el error aquí? Realmente los requerimientos si estaban bien, lo que no estaba era la definición de cada uno, quizás uno englobaba mucho desarrollo o procesos, el cual se podría partir en diferentes brechas o partes para desarrollarlo completamente. Es aquí cuando realmente entendemos que el diseño o la planeación de un proyecto no es un simple a va a hacer esto y aquello, sino la base o esqueleto que le va a dar forma a todo el proyecto. Es como si construyéramos una casa, la cual sin poner cimientos, y al ver que se deshace con cada cosa que agregamos a la casa, hay que estar parchando para que no se venga abajo.

Por ello, les dejo en mente esta pregunta ¿como sabemos que definimos

Continue reading "Es consistente mi PROYECTO?"

Plan, Plan and Plan the project

--Originally published at TI2011 – Project Evaluation and Management

It is important to be prepared for every situation that can be presented throughout a project. So I want to talk about preliminary planning activities in every project, as the chapter 7 (Survival Guide) talks about preliminary activities include defining a project vision, identifying an executive sponsor, setting targets, managing risks and maping strategies. All of this activities are captured in a Software Development Plan.

One o the first things to do in any project is to have a vision and what can be the scope of the project. Defining what the system will do, how it will work, how the developers can develop and code the project will help us to avoid time-wasting.

And let say how important is to make a good plannation, sometimes it can happen this,

Resultado de imagen para train tracks gif

that we are working and coding a project while we are defining what the system are going to do, what things are going to perform, etc. And it is possible while the project is moving on, we need to rewrite or start over some parts that we already did in order to accomplish the requirements or things that we just define at this point of the project.

In conclusion, planning will lead the project to a simpler and good development, avoid that waste of time, locate what our project needs, minimize risks and mistakes. So WE NEED TO PLAN, PLAN and PLAN.