| Scrum Master Location:Allen, TX (Candidate needs to go to Clients office as and when client needed) at Allen, Texas, USA |
| Email: [email protected] |
| From: Amy Jones, Blackapple Solutions LLC [email protected] Reply to: [email protected] Location: Allen, TX (Candidate needs to go to JH &A office as and when client needed) Position: Scrum Master Duration: 6+ Months Job Description: Responsibilities: Improve agile maturity Make sure assigned Teams are adhering to defined Scrum agile process and improving on it Release over Release Desired Outcome: 1. Make sure Teams are adhering to the defined Scrum agile process i. Agile ceremonies (Daily scrum, Backlog refinement, Sprint planning, Sprint Demo and Retrospective) are conducted and action items / roadblocks are followed up ii. Velocity is tracked and used in capacity planning iii. User Stories get into Sprint only after achieving Definition of Ready iv. User Stories are closed only after achieving Definition of Done v. Tasks are created and estimates are updated in a timely manner vi. Team member capacity is tracked and assignments are done accordingly 2. Sprint Velocity for team is improving Release over Release 3. Be the torch-bearer of scrum agile process, and educate team around it Build World Class Product Development Execution Maintain an AZDO burn down which show completing before feature cutoff at all times after sprint one of all releases. This is critical to making sure we can support unplanned items and do not overcommit. There are several ways to accomplish this but the one we've been discussing is using the 50% rule. Also, ensuring Product Managers and Product Owners do not add things to the backlog without taking things out on the basis of Product Board approval. Finally, making sure each team reserves time to do detailed backlog grooming every sprint will help us get better at delivering what we commit to and only having positive schedule/scope surprises. Desired Outcome: Maintain an AZDO burn down which show completing before feature cutoff at all times after sprint one of all releases. We will evaluate this based on Soum's weekly statuses which show the prior weeks burn down. Report release risk and propose mitigation plan Report release risk in terms delivery, quality or scope to management team and propose mitigation plan by working closely with team members Desired Outcome: 1. Analyze Team's progress and raise risk to management as early as possible 2. Call out the impact of the risk and what mitigation plans we have in place 3. Ask for management help proactively if required 4. Analyze past trending and team performance to forecast risk Understanding of application functionalities Understanding functionalities of the application will help Scrum masters participating in the team discussion and to take informed decision. Desired Outcome: Have a basic understanding of the application your assigned Teams are working on Track Release / Sprint planning and execution Make sure Release and Sprint planning are done as accurately as possible based on dependencies, priority and team capacity. Monitor execution and keep team informed in every step of the way Desired Outcome: 1. Make sure stories are constantly refined, so that team can plan better during Sprint 0 2. Deviation between Release commitment and actual stories delivered is minimum 3. Sprints are planned based on Team capacity and stories get into Sprints only after achieving Definition of Ready 4. Deviation between Sprint commitment and actual story points delivered is minimum 5. Track team's progress, keep team and management informed about the progress Deliver World Class Quality Maintain our progress in open production defects. This helps us 1. Reduce customer pain which improves retention 2. Reduce support cost which improves our P&L 3. Increase development cycles which creates more capacity for new capabilities. Desired Outcome: Achieve trailing 6 week averages (by 11/30) 40 Total Open Production Defects <1.25 Open Critical Defects <12 Open High <1 High Open >60 days <1 Critical Open >30 days MINIMUM QUALIFICATIONS Bachelors degree required; advanced degree preferred First level Scrum Master Certification (CSM, PSM I) required; second level certification desirable At least 5 years experience in a Scrum Master role for a software development team that utilized Scrum principals, practices, and theory Minimum of 7 years experience Experience in the transformation an organization of legacy SDLC/waterfall to Agile KNOWLEDGE AND SKILLS Excellent skills and knowledge of servant leadership, facilitation, situational awareness, conflict resolution, continual improvement, empowerment, and transparency Excellent knowledge of well documented patterns and techniques for filling intentional gaps left in the Scrum approach Excellent knowledge of Agile approaches including particularly Scrum, though also Kanban Proven experience with Agile techniques Previous experience acting as a team lead Excellent communication and mentoring skills Experience in working with distributed Team members spread across multiple locations and time zones Keywords: information technology golang Texas |
| [email protected] View all |
| Tue Oct 03 21:10:00 UTC 2023 |