Workflow

GSA SmartPay Workflow

Definition of Ready (for grooming)

• Content has been reviewed / approved by SmartPay

  • Content checklist
    • Accuracy review
    • Style guide review
    • 🔒Content audit review (check notes for broken links, accessibility issues, etc.)
    • Is the content repeated elsewhere?

• User story has clear acceptance criteria

Before grooming

• Product owner identifies the next group of stories to be worked
• SD reviews the stories and documents any questions they might have

During grooming

• Product owner presents story
• Q&A – document any answers / decisions in the story
• Acceptance criteria is refined (as needed)
• UI design / layout decision documented
  • Add Design needed tag = new design layout is needed (ping SD, if needed)
  • Tag or note in story: Copy layout of existing website
• Any other engineering pre-conditions identified
  • Does this need any editorial / best practices content review by SD?
  • Does any content (text, images, video) need to be created?
  • Add front matter (metadata)
    • GitHub issue #
    • title
    • path (e.g., smarttax/common-questions
    • sidenav (e.g., SmartTax)
    • category (e.g., smarttax)
    • tags (e.g., state, tax, help)
    • List assets (e.g., images and alt text; videos)

Ready for Engineering

• Once everything (content, layout, meta tags, pictures, etc.) that is needed for an engineer to work a story, it needs to be communicated that it is “Ready for Engineering”
  • Decision for team: tag or new column