/
2022-06-01 Promo Hero PoC Demo

2022-06-01 Promo Hero PoC Demo

Owned by Julia Boyarshchikova (Deactivated)
Last updated: Jun 02, 2022
2 min read

Participants

Reckitt (RB):

  • Nathan McKean

  • Nick Harris

  • Maciej Sobocinski

  • Katarzyna Lewczuk

  • Rodoslaw Kowalewski

  • Pawel Ploneczka

  • Robert Ruszczyk (contractor)

DataArt (DA):

  • Nikita Pyshnyak

  • Anton Merkulov

  • Sergey Kiselov

  • Nikita Puzyrenko

  • Julia Boyarshchikova

  • Alexander Kostylev 

 Action items

 

To split the list of components in Storybook by ready/not yet ready @Sergey Kiselyov (Unlicensed)
To define success criteria for each component @Julia Boyarshchikova (Deactivated)
The DataArt team have to put more efforts in engaging Nathan and Nick more in the tech decision making process @Sergey Kiselyov (Unlicensed)
The DataArt team have to take their time to fix stuff for several components and then send the list of components to Nathan to check @Anton Merkulov (Unlicensed)@Sergey Kiselyov (Unlicensed)

Key takeaways

 

  1. Success criteria should be added to components as a response to the brief and they should be confirmed. We are adding them into JIRA for @Lewczuk, Katarzyna to access them easily, but I guess we should start from Confluence and confirm them with Nathan first as a next step after Component kick-off, followed by internal interface discussion.
  1. To include Nathan into Component Interface discussion in addition to Tech team. @Mckean, Nathan we have an agreement with Tech team about PR review (including interfaces with props) and it is like 48 hours, so your review should also be aligned with it.
  2. Design system components are developed in the same repository as other components developed by the tech team, though the DataArt team used a separate Storybook for the design system.
  3. The Storybook content can be updated through committing changes to the repository, not through direct editing, which makes updating the content a bit more complicated.
  4. If we want to make updating the content less complicated we should start looking for another tool (e.g. Zeroheight) as a document storage.
  5. We definitely want to make document storage less fragmented so that we could keep the documentation in one place.
  6. Earlier we agreed to have at least one component developed E2E. To this end we need to have clearly defined success criteria for a component so we could test it.
  7. We don't need it right now, but how are we going to address version control?

Meeting recording