Project Everest

Work Update

Feature Driven Development Process for Task Management

by
Krystal Kennedy
Krystal Kennedy | Jul 12, 2017 | in Knowledge Base

Coming into week 2 after an epic first week, jam packed with village visits, the Fiji Fuel Assessment Team were overwhelmed with necessary tasks in order to move into the next phase of prototyping. Being an assessment project, there is a lack of clear direction and thus, we felt it was essential to establish a system that would help us achieve our month goal.

In order to manage our tasks and have a clear outline of the project for July, the team came up with the use of a Feature Driven Development process for task management. The Feature Driven approach is a software development term which involves an iterative process and utilises agile development methodologies in order to produce a high quality outcome.

Feature driven development (hereafter FDD) is a client centric methodology. While usually applied on the context of systems implementation, the underlying principles  and key activities can still be applied outside of software development.

The 5 key activities of FDD are outlined below:

  1. Develop overall model - draft high level notes with the intention of identifying & understanding the fundamentals of what is being addressed. This can be checked and revised throughout the duration of the project. For our project, this has manifested in our overarching goals

  2. Build a feature list - features are small, client valued functions. These are our daily and weekly tasks and have been grouped into related subject areas e.g. R&D (Research) and R&D (Ideate & Prototype)

  3. Plan by feature - involves identifying class owners and feature set owners i.e. Individuals who are held accountable for the progress and completion of a given task or objective

  4. Design by feature - these next 2 step compromise of the majority of the work and involve the actual carrying out of the task

  5. Plan by feature

In terms of task management, the team have utilised this approach and created a spreadsheet shown in Figure 1 below. We started off by identifying the key aspects of the project, see in bold. Underneath these feature sets, we have the relevant tasks/features that need to be completed either daily, weekly or monthly. They have been assigned a corresponding task number for ease of reference and searching.

An ‘Owner’ and ‘Deadline’ are allocated to each task to keep people accountable for a particular action and a day and time they are to have it completed by. We felt that by designating everyone a key aspect to work on, whether it is individual or in a small group, everyone knows what they are required to do, and allows the team to work most efficiently and effectively. We refer to the term ‘All’ as all the members designated to that key aspect and ‘Everyone’ as the whole team.

In the next column, we have included a percentage completion column labelled ‘Completed?’ which gives others an indication of how much that task or action was completed, rather than just leaving the cell blank if the task was not fully completed. Lastly, we have included a ‘Notes’ section in order for users to provide a brief explanation as to why a task may not be 100% completed. We use the term ‘Pass’ in the Notes section if a task was not able to be completed that day and move it to the next relevant day.

(The figure below is a screenshot of the daily Feature Driven Spreadsheet for Task Management used by the Fiji Fuel Assessment Team)

We hope you found this system as valuable as we do and we are open to any suggestions or recommendations to improve this system!

edited on 12th July 2017, 02:07 by Krystal Kennedy

Emma Ridley Jul 12, 2017

This could be a framework moving forward for all assessment-based projects!

Reply 1

William Lee Jul 12, 2017

Love the idea and structure. Will be looking to implement in Water Assessment Vietnam!

Reply 1

Andrew Vild Sep 14, 2017

Status changed to Previous Work
Activity has died off on this thread and so we are working on slimming down ideas for the upcoming activity.

Reply 0