Lubo Drobny

CODE is clean self-documenting communicates the programmer's intentions well designed/structured  ERRORS are handled consistent and transparent way LOGS are appropriate on appropriate level CODE ANALYZER reports no new issues reports satisfactory coverage CODE REVIEW is done CI is green = code is committed to appropriate branches + builds are OK + all unit tests are passing + all integration tests are passing CD is green = build are integrated & deployed OK at staging environments + all regression tests are passing QA initial tests are OK do not report any defects test automation is planned if makes sense PO accepted the story

When is user story ready for a sprint? I think that team should prepare in advance these points: Title - short summary of the story  PO: business requirements (schematic, not novel, priority order) = what & why & when to do? UI: wire-frames or sketches of new UI/UX and flows = how to do it on UI? Dev: architecture & design impact (dependencies, cfg, DB changes, migration, new libs ...) + suggested technical solution = how to solve it on backed and code it? what is impacted? could solution generate technical debt? are we aware of taking some technical short-cuts? CI & devOps impact (Jenkins, VMs, Sonar, Vagrant, Ansible ...) do we need change on CI/CD or envs? QA: acceptance criteria (could be part of DoD) + environments definition to validate PO: clear and understandable DoD (bullets) - fixed for a sprint duration Estimation in story points Links to discoveries (wiki page) or related stories or bugs Fix versions: branches where to commit or merge  Sub-ta