Project Planner

Adding a new project

The new project is created and selected

The created project has no features

The created project has no issues

A feature is created which is linked to the selected project

A issues is created which is linked to the selected project

The project listing has a to-do and issues list as well as a progress bar

The projects features are divided up into their current states

The features can be individually expanded for more information

The projects issues are divided up into their current states

The issues can be individually expanded for more information

A note can be created which is not linked to any projects

Notes are all in one list

Much like the features and issues the notes can be individually expanded

You are able to search individual categories for a specific item

The search results can be expanded for more details

All of the items in the database can be exported to XML found at the given path

This is the result of the projects being exported to XML

All of the items in the database can be exported to JSON found at the given path

This is the result of the features being exported to JSON

Entity Framework Project Planner

This Project Planner was developed in my time training with Sparta Global, it is written in C# and uses Entity Framework with a SQL Server as a backend database, WPF for the GUI and NUnit for the unit tests. The project Planner was developed over 3 sprints using an Agile framework called SCRUM.

The goal of this project was to create an easy to understand program that helps keep track of current and past projects along with and issues and features associated with that project. I also incorporated a note system so the user could add general notes as I often find myself doing. The idea of this project was borne from my past experiences of not tracking projects, issues and features as well as I should have. Consequently causing problems and delays with my own projects.

Development started on this project by creating a project goal, a project definition of done and a user story definition of done. All of these items were drafted and were placed onto my project board which can be found here. Once this was complete I could start my first sprint. I started by creating a sprint goal that I wanted to have completed by the end of the sprint, I then moved user stories from my product backlog to my sprint backlog. Once the user stories met my user story definition of done they were moved into the review column for one of my peers to review.

When the sprint was finished I undertook a sprint review in which I identified which user stories were completed during the sprint, once reviewed they would be moved into done. I also undertook a sprint retrospective where I took note of what went well, what didn't, what I could do to improve and what I would be doing next sprint.

Once I had completed 3 short sprints the project was complete and I undertook a project retrospective which looked at improvements and lessons learnt throughout the project as a whole.

I go into much more detail on all my processes on the github page for this project which can be found linked below.

The project can be viewed on Github here. The Github page contains a download of the final program, my project board, my sprints and sprint goals, mockups, class diagrams and screenshots.