Reflect on Your Experience of Project and Team Management

Tasks for Individual Reflection

This document gives details about the tasks you need to complete individually (NOT with your team). Please see the separate ‘team tasks’ document for details about the team element of this assessment. The tasks are described below in part 1 with the key summary against mark weightings listed as User Acceptance Tests (UATs) in part 2.

1. Individual Tasks

In around 750 words, critically reflect on your experience of project and team management, based on the work you carry out for this assessment in a team. Note: this is an independent piece of work that you must complete on your own, despite references in your discussion to tasks you did with others. In your reflection, include discussions of all of the following:

1. Reflection on technical knowledge gained Reflect on what you learned from this project. Which skills did you find the most beneficial/ interesting/challenging and why, e.g. data analysis, user interface design, coding, etc.
2. Reflection of project against software process model(s) characteristics Consider ways that Agile and/or Waterfall carry out design/implementation/testing and reflect with 1-2 examples of how your team may have adhered to these ways of working or those you did not adopt but feel may have been beneficial based on your experience. E.g. an Agile characteristic is the potential for Pair Programming during implementation.

iii. Reflection of team roles

Reflect on what YOUR role was in the team. Discuss the tasks you carried out with 1-2 examples of how you worked with others to complete tasks, challenges faced, and whether there were any changes to planned roles against reality.

1. Reflections for future projects: lessons learned Summarise your experience with key takeaways. Consider 1-2 examples of what you have learned and how you might approach project/team management again in future projects.

The client, ‘Productive Tech 4 Work’, is a working group of social entrepreneurs united to promote, and track, the use of technology for workplace productivity, such as devices which use Artificial Intelligence (AI). Some initial data requirements for the prototype system being commissioned are described below.

1. Technologies for productivity

The prototype needs to allow developers/technology companies to register their contact details including their name, company address and phone number (where applicable), and email. Once registered, they will use the system to showcase their technologies. Details of each technology should include its name, a description of what it is used for, its setup (e.g. software, mobile app, wearable), and RRP (recommended retail price).

2. Employees in the workforce

The prototype will be initially rolled out for a selection of job types at one participating workplace, before a wider system roll-out [out of scope for this assessment]. Managers of the workplace (a local council in this case) will sign-up to the system, and ask their employees to follow suit, where they will register their names, job type (administrative or managerial, which are the two job types selected for the prototype) and a description of techniques they currently use for productivity, e.g. “I use pomodoro”, “I get coffee every hour”, etc.

3. Tracking ratings for current/potential use of technologies

Once employees are registered, they would browse the list of technologies (read-only) and provide a rating. This is envisaged where employee will indicate their usage from one of three options provided: “I have used this technology”, “I would like to use this technology”, or “I am not interested in this technology”, alongside a rating of 1-5 (1 as a low score, and 5 as a high score). There is also an optional comments field for further details. The intention is that this information will support decision-making in whether managers might invest in particular technologies in the future, how their employees feel technologies are supporting their productivity (or not), etc.