kelatebaru

Thoughts on Engineering Design and Analysis phase, specific to running sprints. Thoughts are based on assumption that PO is ready with sprint items. I. Pre-requisites: -      Understanding sprint requirements: New User Stories Story Specifications Walk through (PO, QA, Dev) Understanding Acceptance Criteria Wireframes walkthrough (where available) Gathering performance and security requirements Walk through of issues to be resolved in sprint and their priorities II. Architecting Process   -      Technical Impact Analysis  (Very Important for running sprints) – Identifying impact on existing application against implementation thought for new stories/issues  -       Planning implementation of any technical change in process/technology based on previous sprint review, retrospective meetings or any feedback from client -        Decision Analysis & Resolution  – Identifying ...

Planning Poker (PP) is among the most popular and effective estimation techniques available today. But  a question here - "How can I play planning poker with teams that are geographically distributed" ? There are likely many options to achieve this. Sharing a few common ones below: Option-1: Chat Window (Tried, but leaves loop holes for biased points selection) It is implied that communication mediums like GoTo or WebEx are used when teams are geographically distant. Once the requirements are clear, product owner can signal via an utter to give points and every member can use chat window of tools to put a number and hit enter. Option-2: Webcam (I'm using this one in current project - Not great fun, But works!) If communication medium used supports video conference with multiple people (Google+ video a free and popular one), one person takes responsibility of saying 1-2-3-Go and as soon as "Go" is said, teams can show up their cards on webcam. Since tools support...

Compiling 10 things to remember in sprint cycle (from theory and experience), which anyone following scrum anywhere, should remember!! 1. Spirit of Scrum says work and think using “We” and not “I” (No blame game and be ready always to lend a help, if it helps in completing sprint successfully) 2. There is nothing called “The Sprint partially succeeded” . It fails or succeeds in full i.e. all tickets must be delivered well and in time (think of DB transactions as analogy ) 3. Whenever you find yourself stuck on account of dependency, approach Scrum Master ASAP. 4. Following processes may sound boring. And following a new process may look a burden. But remember, it is We only who’ve defined process and should hence follow it for sprint betterment. 5. Keep standup short – What I did? What I’m doing next? Am I facing any issue or  has to discuss anything (after standup)? 6. Talk in numbers – Prefer JIRA (or whatever tool use) task numbers with a very small description for sta...