Part II. Process
Itâs Tuesday, and Rick, Mark, Olga, and Arti are standing at the whiteboard, looking at a wireframe that theyâve drawn. Arti has a marker in her hand, but sheâs not drawing. âRick, I donât understand what youâre driving at. Can you explain the problem?â she asks.
Rick takes the marker, wipes clear a section of the board, and explains the regulation, again. The team is designing an app for stock traders, and the app must obey a strict set of regulations. Rick, the business analyst, is responsible for making sure that the teamâs designs support the rules.
After a while, the team is nodding, and Arti takes the marker again. She suggests a change to the wireframe design of the app on the board and the team nods again. They all take out their iPhones, take photos of the board, and agree to reconvene the next day. Theyâre confident that what theyâve agreed on will be ready for user-testing on Thursday.
Arti, the designer, goes back to her desk to begin detailing out the design theyâve sketched. Mark, the frontend developer, begins building the pageâhe uses components from the Design System the team has built, so he doesnât need to wait for Arti before getting the basic pieces in place. Rick opens the projectâs wiki page and begins to document the decisions the team has made about the applicationâs behavior. Heâll review these choices with the product owner later in the day. And Olga, the QA tester, begins the process of writing tests ...