Part 3 of the "How to build the best Software Products" Series, brought to you by Blossom.co
Examples & best practices for a continuous workflow covering the activity of each role in a software team.
Roles:
1. Designer & UX
2. Engineer
3. Marketer
4. Product Manager
Additional:
5. Activity & Reports
4. 1 Designer & UX
Designer & all involved team members collect research
material in various formats.
!
Tip: Research in the UX phase, but add information as well
continuously throughout the whole process.
5. 1 Designer & UX
Profound research …
!
• lets the team understand a feature very well
• simplifies the upcoming process
• leads to higher quality results
13. 2 Engineer
Blossom Integration with GitHub (recommended):
!
Create a new git branch, push it to GitHub and connect it
to the Blossom card.
14. 2 Engineer
Blossom Integration with GitHub (recommended):
!
Code updates get synced automatically and are visible for
all stakeholders in the card and in the daily digest.
15. 2 Engineer
If a slot is open in the “Review” stage, the card gets pulled
into it and the review process starts.
16. 2 Engineer
If a slot is open in the “Review” stage, the card gets pulled
into it and the review process starts.
20. 3 Marketer
If a slot is open in the “Marketing” stage, the marketer pulls
the card into it and starts the marketing process as defined
in the marketing policy.
21. 3 Marketer
If a slot is open in the “Marketing” stage, the marketer pulls
the card into it and starts the marketing process as defined
in the marketing policy.
41. 5 Daily Activity Digest
You can use the Daily Digest for the daily standup meeting
or to forward the current status for example.
All actions that happen
throughout the process are
delivered directly via a daily
activity digest to your
inbox.
42. 5 Activity Notifications
If you have messaging tools like Slack, Flowdock or HipChat
connected to Blossom you can get instantly notified about
important events and never miss a thing.