Scrum Master

Job Description

Roles and Responsibility : Backlog MaintenanceCreate and Manage BacklogBacklog grooming: Manage/ Update sprint- backlog and project- backlog regularly after client calls and demosPlans forward- looking technology investigations (spikes / POC) After each sprint- demo work with the dev team to estimate and re- estimate backlogFacilitate prioritization of backlog first time;Facilitate prioritization of backlog during planning n+1 sprint with clientCreating mock- ups/ wireframes/ Sketch images to illustrate or to detail for getting clarity from the client, and for communicating the task to the dev teamUse JIRA for all backlog (no use of Google spreadsheets) Daily Stand- upsDrive daily- stand- upsAsk what was done yesterday, what is the plan for todayAsk probing questions in the stand- ups and outside of itIdentify potential roadblocks or challenges that may come upConsult Group Lead and raise your concernsImplement advise by GLEnsure that the team is working towards completion of the sprint; each stand- up well did, will suggest if the velocity is enough to complete Sprint or no(Maintain and) Update the information radiator board (with stickies) for all sprints Sprint DemosRun sprint demosCalls must be marked on client and team s calendar; no ambiguity in when calls happenEvery member must be present on calls at least 2- mins before the scheduled time on the calendar; be the first to join the call as moderatorIf you are unable to join, ensure that the session is recorded; if it cannot be recorded, ensure the team has captured all feedback during the demo Business AnalysisUnderstand the business of the client and the projectThis will enable you to question business needs that clients communicateValidate and record agreements in stories, acceptance criteriaCreate mock- ups/ wireframes/ Sketch annotations to illustrate or to detail - - for getting clarity from the client; and for communicating the task to dev team - - put these in stories in JIRA Project ManagementThe plan - - Do - - Check - - Act (Complete control on the project) Create Physical boards information radiator board (with stickies) Plan deliverables (JIRA/ Sprint) along with the teamOrganize the Sprint, get re- estimates done,Plan Sprint n+1 with the client - - prepared stories for the n+1 sprint to be taken up by dev team; work with QA inLearn to read JIRA Burndown Charts to know if the project is on time or is there likely to be a delayIf there is likely to be a delay, speak to the Agile Coach / Group Lead to decide the nature of communication to be sent to the clientRelease Planning - define release goals Quality AssuranceDetail out stories with acceptance criteriaEnsure all stories have acceptance criteriaWork with QA in improving quality of acceptance criteriaWork towards zero- defect sprintsDefect triage - accept/ rejectSupport the Dev+QA team in testing yourselfUse JIRA for all these activitiesDrive testing strategyDeliver stories in piecemeal for testing throughout the sprintValidate technical architecture by asking relevant questions Stakeholder ManagementSend out weekly Status emails to internal and external clients - - must be on SM s calendarRed, Amber, Green statusBudget consumptionKey activities this weekPre- empt and document roadblocks that you/ team foreseeRaise/ Flag issues to clients and work aggressively within the team/ org to mitigate thisCoach clients on agile/ scrum, our model, align them on our practices, using Jira, etc Engineering PracticesDrive towards Unit TestingDrive towards Continuous Integration (CI) using Jenkins; leads to a clear release and deployment strategy/ planPiecemeal UAT strategyDrive Intrinsic quality like Code, stories written, test scenarios writtenContinuously monitor and improve them. Question people on themUse Jira rigorously to track stories, defects, and manage it end to end. People, Process and Tool CoachCoach people to improve in their roleChallenge and question people on the way they are working to make it betterRun sprint- retrosDuring retros listen for cause behind the words; by asking probing questionsContinuously strive to improve yourselfHandhold team on Scrum way of doingStrategize which tool to use for what purposes.,

Keyskills :
testscenarios externalclients continuousintegration technicalarchitecture drivetesting it qa uat red jira agile scrum charts listen triage testing jenkins control clarity tatementsofw ksow