In the last blog post, we looked at the initial interview and how you can use the Power Apps Map (PAM) to create a solid foundation for your low-code project. If you don't know the PAM yet, you can use it directly as a Miro template here:
Now we move on to the next step: defining the project team and documenting roles and responsibilities.
Why is the project team so important?
A successful low-code project is teamwork. To ensure that everyone can work together efficiently, the following should be clarified early on:
Who is involved?
What roles are there?
How do we want to work together?
Where do we document our progress?
💡 Tip: In the Power Apps Map there is a separate area where you can record everything compactly.
1️⃣ Define project team & roles
Every project is individual, but the following roles have proven to be useful:
👨💻 Developer – implements the technical solution
🔍 Tester – tests the solution & formulates test cases
📌 Product Owner – sets the requirements & prioritizes
🎯 Coach/Consultant/Project Manager – structured & provides technical & conceptual support
💡 Practical tip: The Product Owner from the department and the end user should be directly involved !
2️⃣ Set collaboration mode
How do we work together? There are two proven approaches:
🔄 Agile approach
📌 Goal: Maximum implementation with the available resources (budget, time)
📌 Flexible scope: We implement as many features as possible, but have a fixed budget.
📏 Classic approach
📌 Goal: A fixed range of functions should be achieved
📌 Variable resources: Effort can and usually will change.
💡 My tip: Choose a method and adapt it if necessary.
3️⃣ Regular appointments aka Jour Fixes
Think together about how often you want to synchronize with each other, exchange work statuses or plan new work. Such breakpoints can be particularly useful in a "remote-only" environment. However, make these appointments with a sense of proportion so that they do not get out of hand (death by meeting).
Here is an example from one of our past projects:
Every two weeks on Mondays 08:30 - 09:30: Review
Benny, Kai or Nöhre (requester and tester)
Marcel, Maik or Kim (developers and consultants)
Review new functionalities & put together upcoming work package
Every two weeks on Mondays 1:30 p.m. - 4:30 p.m.: Retro (1 hour) followed by Sprint Planning (2.0 hours)
Marcel, Maik & Kim (developers and consultants)
Reflect on the sprint (4L) & define a new goal for the next two weeks
Daily 08:30 - 08:45: Daily Stand Up
Marcel, Maik & Kim (developers and consultants)
Discuss daily goals & resolve blockages
4️⃣ Manage communication & file storage
✅ How do we communicate? Teams, email, chat groups, only in regular meetings?
✅ How do we document tests, feedback & decisions? For example, should test results be sent directly to the developer via Teams or do you want to document this in an Excel list or planner, for example?
✅ Where do we store project documents? These questions seem trivial, but you should decide on them together. Especially when it comes to documentation, agree on a platform/tool that everyone can handle, so that it is not a hurdle for anyone to store important project documents properly.
💡 My tip: 🚀 Keep it simple! Agree on a platform – be it Teams, Confluence or so.
5️⃣ RACI matrix for clear responsibilities
The RACI matrix helps to clearly clarify responsibilities:
🔵 Responsible (R) – Implements
🔴 Accountable (A) – Responsible for implementation
🟢 Consulted (C) – Is consulted
🟡 Informed (I) – Will be informed
Depending on the task in the project, these four dimensions can be used.
Below you can see an example from a past project of ours:
Conclusion
With a well-structured project team , defined roles & responsibilities and a clear collaboration model , you ensure that your low-code project runs efficiently.
📌 The next blog is about the next step: "Profile - What is it now?"