N4SJAMK Workflow

Basic scrum

• Iteration cycle of two weeks (sprints)
• Not everyone is at work 5 days a week
• Integrated Review & Planning day: will most likely take the whole day
  • Feedback + Demos (what did you do, explain in layman terms, some simple visuals?)
• Ticket management
  • Person responsible is assigned during the Planning session for each task / ticket, so that there will be no questions
  • ZenHub or Trello? ZenHub is fine (GitHub integration)
  • Backlog, Doing, Review, Done
    • Tickets from Review & Done are handled in the biweekly meeting session. Tickets that are deemed ‘complete’ are then removed from the board (closed). Tickets can be reviewed (and should be) even during the sprint.
• Biweekly meeting session (15 minutes, standing up or whatever)
  • Explain your problems and stuff you might’ve faced during the week, what have you done and are doing
    • What have you done
    • What will you do next
    • Any problems?

Job Stories instead of User Stories

• Tickets / Tasks are made from them in biweekly Planning sessions
  • Explain?? How do they differ from user stories

User story: As a (person) I want to (action) So that (expected outcome)

Job story: When (situation) I want to (motivation) So I can (expected outcome)

• Job stories are made from data gathered from sd/ux iterations
  • How do these iterations work, do they run alongside our scrum iterations? What do these iterations do? Do they differ from basic scrum?

Responsibilities

• Who is responsible and for what, how is work organized: here need commentsand improvments

Management

• Paavo??

Service Design / UX / Graphic Design

• Heli
• Paavo

Operations / Administration

• Jarmo
• Henri
• Tero

Development

• Teemu
• Janne
• Paavo
• Taneli ??

Testing

• Pete666