This second sprint of my project is focussing on the back end platform of Metronet that will allow networks to manage and improve their services.

Earlier in this semester, I had planned more time for it, however, I feel the scope of sprint 1 increased, causing me to have to tighten the time frame for this sprint. Due to this, I first wanted to scope the sprint out and decide what steps and outcomes I wanted to achieve from it.

I started by just getting some thoughts down in FigJam.

image.png

With a rough outline set, I next wanted to develop out some proto-personas to work from. I had roughly identified these in semester 1 during the desk research phase, but I now needed to expand on them.

I also considered that there would be a fourth user group, that being those in charge of managing personnel within the networks, however I decided exploring this could be considered out of scope as I felt 3 was already a lot, and it was the least interesting or nuanced design challenge.

Screenshot 2025-12-14 at 13.43.23.png

I was pleased that I was able to identify the scoping and timeframe issue with this sprint and react to it appropriately. I feel management of time and scope creep is something I’ve been able to develop over this year well.


FigJam Board

https://www.figma.com/board/jdy3p72qOWZ6FzGhvTBl0T/Metronet-Conductor?node-id=0-1&t=OE8hCmCUtM0lPUFE-1


With my scope outlined and users decided I now wanted to revisit the process mapping from earlier in the year.


← PREVIOUS PAGE

NEXT PAGE →