2 minutes read
We wanted to share with everyone how we use Agile methodologies to release new features and get feedback on our release process.
We use 2  weeks sprints, and below are the meetings and details of our process: 
Sprint Planning – 1-2 hours
  • Product Owner presents all the stories for the current sprint (what/why do we have to implement) to all team members (DEV/QA/UX)
  • team asks questions to the Product Owner to clarify all stories
  • team estimates each story based on complexity (risk of the implementation, areas impacted by the change, UX designs, QA manual and automation)
  • each story should have a driver and UX, DEV and QA tasks (see below for a full list of tasks)
  • team commits to a list of stories to deliver in the current sprint
Mid Sprint Demo – 1 hour
  • team meets with product owner to show progress and current implementation
  • gets feedback from product owner on current implementation
  • QA presents status for all stories, confidence and risk
End Sprint Demo – 1 hour
  • team presents to product owner final implementation and gets feedback
  • QA presents status for all stories, confidence and risk
Scenario Testing – 3-4 hours
  • the team tests different user scenarios/workflows (different type of users – edge cases)
Sprint Retrospective – 1 hour
  • Start, Keep, Stop doing
  • what went good/bad in current sprint
  • choose only one thing to improve in the next sprint
  • check during next sprint if the item chosen to improve is going in the right direction
Default Story Tasks (every story should have after planning ends)
  • DEV: (if needed) discuss with other teams potential implications
  • DEV: (if needed) Create documentation
  • DEV: Start implementation based on current documentation and designs
  • DEV: Code review
  • QA: Write test plan (wiki page – choose which tests can and makes sense to be automated)
  • QA: Automation: implement/update tests or test scripts from current test plan – (UI, Performance and Load testing, Security)
  • QA: Manual: test the implementation (after code review) – (UI, Performance and Load testing, Security)
  • DEV: Bug Fixing
  • QA: Bug Regression
Definition of Done (every story is completed after it meets all items in the definition of done)
  • DEV and QA complete
  • Automation
  • i16n/localisation
  • release notes
Please let me know your thoughts, ideas, comments.

How Much Traffic Can Your Website Handle?