Scrum Master I

Scrum Master,Agile Methodology,Jira,Healthcare ","description":"

Role Proficiency:

Partner with up to two business and technology teams to plan and execute tactical and strategic efforts; delivering the business vision.

Outcomes:

1. Team coordination: Ensure teams operate to agreed team cadence. Provide support to help teams reflect learn and improve on their Agile practice
   
2. Dependency coordination: Support teams to ensure smooth collaboration among extendedteam members wherever required and enable clear visualisation of dependency blockers
   
3. Track and manage team Visual Management Boards: Help teams maintain their team data and collateral; keeping them relevant over time to changing needs of the business
   
4. Continuous improvement: Provide mentoring support to Product Owners and team members to refine their understanding of Agile practices
   
5. Support Product Owners in each team to engage inform influence and negotiate with stakeholders using product backlogs (prioritized based on value) as the basis for discussions.
   
6. Work with the Agile coach to ensure alignment to Agile values and principles.
   

   
   

   Measures of Outcomes:
   

   
   
   1. Percent of increase in Agile maturity as defined by the maturity tools i.e. adoption of Agile practices and participation within the team
      
   2. Percent of achievement in OKRs or KPIs as defined for project \/ program
      
   3. Number of contributions to Scrum Master guilds to improve Agile adoption; creating sustainability
      

      
      

      Outputs Expected:
      

      Change Agent:
      

      
      
      1. Facilitate team events to drive Agile practices (e.g. daily stand up sprint planning sprint reviews and sprint retrospectives).
         
      2. Conduct regular check- ins with all team members to provide performance feedback and offer coaching and mentoring
         
      3. Create and maintain team metrics to monitor and measure teams performance (e.g. Velocity Burndown CFDcycle time etc)
         
      4. Coach the team the product owner and business stakeholders on Agile practices and processes (e.g. methodology acceptance criteria user stories estimation etc.)
         
      5. Provide training for the team on Agile concepts various practices and frameworks as required
         
      6. Effectively use a variety of collaboration tools (e.g. Mural Miro MS Teams Zoom etc) to stimulate collaboration and transparency
         

         
         

         Skill Examples:
         

         
         
         1. Understand the business requirements and interact with SMEs at various stages of development
            
         2. Understand the customers technology landscape and requirements
            
         3. Identify improvements for the release management process release schedule and plan
            
         4. Understand RACI Matrix and Governance Framework for related projects
            
         5. Promote continuous knowledge management
            
         6. The ability to cut through unnecessary work and focus only on the essentials
            
         7. Exhibits sound judgment under pressure with the ability to remain calm under stress
            
         8. Possesses motivation and coaching skills; guiding and supporting teams throughout a project
            
         9. The ability to think and make decisions quickly in rapidly changing circumstances
            
         10. A true Servant leader with the relevant skills and competencies
             
         11. Demonstrate conflict resolution skills to effectively facilitate the team business stakeholders and project delivery.
             

             
             

             Knowledge Examples:
             

             
             

             
             

             
             

             Additional Comments:
             

             
             

             Project Management Methodology Understanding of various project Management methodologies and processes, specific skill on Agile Delivery Model Awareness of how the Project Schedule is set up and used Program plan, Release plan for the project Sprint Planning Ability to effectively collaborate with the team, product owner, and stakeholders to establish clear goals and priorities for the sprint. It includes understanding project requirements, estimating work efforts, and ensuring that the sprint scope is feasible within the teams capacity. 1) Understanding of Backlog: Ability to review and comprehend the items in the backlog, prioritizing them based on value, urgency, and dependencies. 2) Defining Sprint Goals: Collaborating with the team and product owner to define a clear, actionable goal for the sprint, aligning it with project objectives and stakeholder expectations. 3) Estimating Effort and Capacity: Using estimation techniques (e.g., story points, hours) to assess the effort required for each backlog item, considering the teams capacity for the sprint. 4) Task Breakdown and Definition: Breaking down high-level features or user stories into smaller, more manageable tasks and ensuring that each task has clear acceptance criteria. 5) Facilitating Collaboration: Engaging team members to discuss dependencies, potential blockers, and technical considerations, ensuring everyone is aligned on sprint priorities and tasks. 6) Commitment and Focus: Ensuring that the sprint goal is realistic and achievable, and fostering team commitment to completing the work by the end of the sprint. 7) Time Management: Managing the time during sprint planning effectively, ensuring that discussions are focused, all necessary items are planned, and the sprint backlog is refined. Risk Management Managing risks using RAID - proactively manage uncertainties that could potentially affect outcomes: - Risk Analysis: Ability to assess risks, evaluate their probability\/severity and quantify their impact. Awareness and usage of tools like brainstorming, SWOT analysis, and risk assessments. - Problem-Solving: Ability in developing creative solutions to mitigate risks and reduce their impact on the project or organization. Collaborate with peers in understanding how similar risks are handled - Communication: Effective and on-time communication of risks, strategies, and mitigation plans to right stakeholders. - Project Planning: Skill in using project plan which contains risk management activities within critical path and using this to drive stakeholders in making critical actions to ensure risk avoidance. Status Reporting Ability to set up a process to collect from various tracks, and report on a weekly basis, a structured and transparent status which keeps the key stakeholders aware of current status, planned future work, potential issues\/delays\/dependencies and any asks\/help from leadership. This helps in proactive decision making and gets the team focused help in resolving things which could be outside span of control. Governance Governance - Frameworks, processes, policies, and decision-making structures that guide, direct, and control the functioning of the account\/project to ensure it achieves its objectives, remains aligned with its goals, and operates within established standards and regulations. Awareness of Decision-Making process, Cadence, Communication Protocol, Compliance requirements - legal, regulatory, and ethical standards. Quality Management Focus on embedding quality into every phase of the Agile process, from planning to delivery, and emphasizes collaboration, iterative testing, and customer feedback to ensure high-quality software. 1) Understanding Agile Quality Principles: Knowledge of core Agile principles that promote quality, such as delivering working software frequently, focusing on customer satisfaction, and continuously improving processes. 2) Collaboration with Stakeholders: Actively involving stakeholders, including customers and team members, in setting quality expectations and providing ongoing feedback throughout the development process. 3) Defining and Implementing Quality Metrics: Ability to define measurable quality criteria, such as defect rates, code coverage, and performance benchmarks, and track them consistently across iterations. 4) Continuous Integration and Continuous Delivery (CI\/CD): Implementing automated build, integration, and deployment processes that enable frequent and reliable releases, ensuring that quality is continuously verified through automated tests and builds. 5) Refinement and Retrospectives: Facilitating continuous improvement through regular retrospectives where the team reflects on quality practices, identifies areas for improvement, and adjusts workflows and processes accordingly. 6) Customer Feedback Loops: Engaging with end-users or stakeholders to gather feedback, identify improvements, and adjust features or designs to meet customer expectatations. ","