Stakeholders - AgileBusinessAnalysis/01_TEAM GitHub Wiki

The Wisely team has six main stakeholders to consider during these three sprints of the project:

User

Our potential users mainly are people in a long-term relationship. Most of these people are looking for support to improve or liven-up their relationship. During this project, the potential users are predominantly included in the validate stage. Their feedback helps the team to improve the MVP step by step as well as raise concerns or ideas that we have not considered yet. The feedback is discussed in the team and added to the product, and subsequently sprint, backlog according to priority.

We obtained information directly from the stakeholder either face-to-face in personal conversations or over contact via digital communication means. To validate our results and gather feedback from users, the users received a link to the digital prototype and a digital feedback form where they could directly input their opinion in a structured way. In most cases, we contacted potential users to which we already had established personal contact, so we could approach them very openly and gather very direct feedback.

Supervisor

Our supervisors are the lecturers from the course "Agile Business Analysis": Knut Hinkelmann, Holger Wache, Beat Fräfel and Maja Spahic. The supervisors are predominantly included in the sprint reviews. Their critical feedback on the previous sprint helps the team reflect and plan the new sprint by integrating the lessons learned accordingly. Thus, the feedback is added to the product, and subsequently sprint, backlog.

The supervisors were contacted during the coaching sessions on a face-to-face manner. The figured as the stakeholders for the Sprint Review meeting of each sprint and were presented with the current state of work and asked for any general feedback and improvement potential.

Sponsor

As discussed in the section "Project Sponsoring", business angels or venture capital firms could be possible sponsors of this endeavour. The sponsor would be updated after every sprint to share recent developments and possible challenges. Additionally, in case of issues, sponsors could also be involved on-the-spot to provide support. The feedback from the sprint updates or from other involvement is discussed in the team and added to the product, and subsequently sprint, backlog.

Real sponsors were not a part of the project, due to the educational environment and nature of the project. Nevertheless, the supervisors figured in a way as sponsor in their role during the coaching and Sprint Review sessions.

Developer

Good app development is important to meet business needs. End-users sometimes create an unrealistic list of features and requirements. The developer shapes and builds the solution and is responsible for the development. Its job is to find a way to fulfil as much of the “wish-list” as possible while meeting business goals. It is important to understand the requirements and translate them into a solution that meets functional and non-functional needs. The developer is allocated full-time to the project. Its responsibilities are working on the solution & testing the output.

We did not work with external developers during the project and we ourselves figured as the developers. It was the responsibility of the Project Owner to ensure that the Developers/Designers conducted their work according to the elaborated requirements.

Marketing (team)

Their job is to understand the company, the brand and the clients. The marketing team will provide the company's brand guidelines. They will be an approval point for marketing strategy, communication strategy and digital strategy for Wisely's projects. The marketing team would be engaged early and often within the project, to approve all the marketing aspects.

Marketers or a whole marketing team were not a part of the project, due to the educational environment and nature of the project.

Director/Partner

Director/Partner launch projects, fund projects, kill projects and determine when projects are complete. No other group of stakeholders is likely to have as much power over project scope and deliverables as the Director / Partner.

A director/parter was not a part of the project, due to the educational environment and nature of the project.