Purencool Itickets project planning methodologies

To create a project that has a large vision you need to be able to place it in a process so that it can be tested, reviewed and implemented. The software industry is not any different. The methods software agencies are using now are feature based software and it really works well. The ability to plan and move quickly to deploy software on an iterative basis is important as this allows progress to be made and priorities to be set. Purencool Website Development are always refining their techniques and this post will give the customer an indepth look at the new process in place to finish projects that are managed by Purencool.

Vision Document Template

All projects have a vision and this is important, but it needs to be written down in a format that is easily understood and able to be accessed by all stakeholders. It keeps the project focused and moving in a direction that the client purposes and giving Purencool foundation tools to complete the online reality. Purencool has always had a vision document that we used and below is a copy of your Vision Document. Once the vision document is completed it then needs to be placed into a system that allows the development of the software. There are many different ways to do this and we are now moving to Agile type of methodologies.

Agile Epic Stories 

Purencool Website Development are not Agile experts but the methodologies of coding a large website development in features is really appealing, it helps with customer service and to be able to create and maintain software at a quick rate. When you first trial anything new you always do it badly but with implementation over time it becomes more effective, now the vision document is complete it is time to start creating  Epic stories. An epic story is an overview of a person that is using a product or service and it explains what they do in the software and how it is to react. An example of this is the Purencool-Iticket login user (see here) what you will notice is that all it discusses in a broad fashion is what the user needs to achieve. Once that is complete and all the information is drawn out we have to take the information and theme it. 

Agile Theme Stories

Once you have the epic stories of each user under control then you are able to create themes. They are exactly what they say they are different themes that are filtering though the project, an example of some themes are an ecommerce shop with a blog. Each of these themes are used by a user but have different objectives but are a part of the epic story gleaned from the vision document. Finding the themes in your project has multiple benefits, code is not being recreated and it helps with an overview for the next step to be completed in the project setting the scene for user stories. To see an example of Agile themes, Purencool-Iticket has one here

Agile User Stories

An agile user story are small clear statements for a developer to create software. For example using the ecommerce shop with a blog again, the developer would not just get a card that said 'create a blog' and he then builds the elements of the blog using ESP (extra special powers). The statements need to be in context for example if you were to develop a blog and it described the features clearly. For example one statement might be,

"The user when entering the blog has to be able to view the 'Title' at the top of the page. The content needs to be in the middle and under the main content the user will be able to access three older posts using a link."

When done this way it becomes more communicative and easier to understand. A user story in affect describes an element of the theme and are never very long. To see an example of this have a look at Purencool-Iticket users Agile stories. If you would like to know more please contact purencool website development and we will assist in reaching your online goals