Project planning

Definition & use
Well planned activities lead to excellent results and eliminating deviations in time. Having already defined the project, agreed upon optimal methods and technologies, project planning for software development is now possible. Relevant milestones and checkpoints will be set and drawn on the reference project plan. Time schedules, teams involved and specific tasks are to be designed and agreed. Any deviation will be notified and analyzed, leading to a dynamic adjustment of the plan. This stage is of major importance both for the client and the engineers team for it is a final step in the contract and it organizes both parties resources (human and financial).

Codespring approach
If someone could not establish a fix reference project plan, we at Codespring are strongly motivated to work on its basis because even when being out in the XP (Extreme Progamming) reaching specific milestones will give all parties satisfaction and the feeling of being on the right track. It is the certitude that resources have been well distributed and that the project is working well. Project planning at Codespring is like the ticket to the desired destination.

Examples:

1. Client: various production units, PRODUCTIS project

Project Planning in the case of Productis project applied Agile methodologies,. Thus  we are working in two weeks iterations, always having a fully tested and deployable version at the end, ready for client feedback, making sure we are on the right track on shipping the desired solution. The required features are well defined into user stories, and split using the Poker planning method into relative story points. Having a well defined and experienced team, the velocity is estimated, and by knowing iteration’s length in time, a schedule is being created. At every iteration start the user stories are chosen for development, by knowing their priorities and the team’s velocity. If the requirements change, or we learn more about the given business, a new estimation is done.