Experience Recommendations - Secure FY20-Q3 - Day-1 Experience for people to using Security features
#34368 (closed)):
Recommendations(This is the recommendation for1. Vision for Group-level dashboard Day 1 experiences: make it easier for the user to configure security scans for different projects so that the user can use the dashboard, step by step breakdown could be:
- Copy changes, make copy tell user clear: What is the current status, what user can do next (#200003 (closed))
- Give clear instruction(such as CTA) to redirect user to go to certain project configuration page (#200003 (closed))
- Improve configuration available on group level: maybe a simple toggle switch (#34771 (closed))
- Make “Configuration available on group level”, let the user directly enable scans on dashboard page with simple toggle switch (#200004 (closed))
2. Vision for Project-level dashboard Day 1 experiences: make it easier for the user to configure security scans of current project so that the user can directly use dashboard, step by step breakdown could be:
- Copy changes, make copy tell user clear: What is current status, what user can do next(#200003 (closed))
- Give clear instruction(such as CTA) to redirect the user to go to the current project configuration page (#200003 (closed))
- Improve configuration available on group level: maybe a simple toggle switch (#34771 (closed))
3. Suggestion No.2 for the same for container scan and compliances page
#35234 (closed))
4. Highlight “Ultimate feature” right after user upgraded (#34771 (closed))
5. Configuration page improvements: (- Configuration show clear each scan on which branch
- Simple toggle switch for turning on security scan on all possible branch
- Show user configuration status: not yet configured, configuration is in process, configuration is failed
#34400 (closed))
6. Make project-dashboard and group-level dashboard easier for user and make the status of project-scan clear: (Experience Recommendations Checklist
-
After completing the UX Scorecard for a JTBD, create a “{{YYYY}}{{Quarter}} Recommendations for…” issue for each JTBD and include them in the Part 2: Experience Recommendations sub-epic. -
Brainstorm opportunities to fix or improve areas of the experience -
Create an issue for each recommendation and link them to the corresponding JTBD recommendations issue. -
Think iteratively, and create dependencies where appropriate, remembering that sometimes the order of what we release is just as important as what we release.
If you need to break recommendations into phases or over multiple milestones, create multiple epics and use the Category Maturity Definitions in the title of each epic: Minimal, Viable, Complete, or Lovable.
Edited by Camellia X Yang