5 Agile Tips / Techniques

  1. JOBS STORIES vs USER STORIES
fig.1 User Story
fig.2 Job Story
  • If you had to guess each crash monetary cost, what would it be?
  • And the effort spent on finding, fixing and testing bugs?
  • What about the client behaviour getting the app crashing on their face?
  1. We are going to work in pairs (1 QA & 1 Dev or 1 UX & 1 stakeholder, etc).
  2. Each team will get points/scores for each crash, bug and minors they find.
  3. The winner takes the trophy. (Motivation)
fig.3 Good, Bad, Ugly
  • by Workflow,
  • by Business rules,
  • by Major Effort,
  • by Complexity,
  • by Data,
  • by Entry Methods,
  • by Platform, Generic/Custom,
  • by User, Spikes.
  1. Previous Sprint Goals.
  2. Previous Sprint Retrospective (Keep/Stop/Start doing or Good, Bad & Ugly).
  3. Sprint Retrospective (Actual — same method)

--

--

--

Engineering | Agile | Climbing | Travelling

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Getting started with AWS for Unity

Tryhackme: AgentSudo

API Based Data Ingestion Using Local Nifi

AWS Certified Solutions Architect — Professional Passed on Oct 2019!!

Week in Review: The PMP Change Is Less Than 90 Days

Let me tell you about Customer Success Engineering

Start PostgreSQL on WSL Startup

5G/MEC enabled applications with AWS Wavelength

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Nicolas Quartieri

Nicolas Quartieri

Engineering | Agile | Climbing | Travelling

More from Medium

5 essentials you should consider when writing a user story

Understanding the 12 Agile Principles — #7

What the heck is Velocity and how do I use it?

4 prerequisite conditions to start with Scrum