| Scrum Manager - Seattle, WA (Onsite) - Long term at Seattle, Washington, USA |
| Email: [email protected] |
| Hi Team, Please find the below job description and send t quality profiles ASAP. Role : Scrum Master Location : Seattle, WA (Onsite) Duration : Long term Please submit Only locals and Independent Contractors (Willing to relocate also fine) Job Description: To bring additional clarity to the Scrum Master role within INTL Commerce/Community teams, we developed this list of focus areas. Sprint Management: Act as lead team spokesperson on delivery related items with responsibility for communicating the story of the sprint, including delivery stats, overall trends, etc. Maintain accurate and projected capacity plan at all times. Ensure appropriate backlog refinement activities are taking place to maintain at least 1 sprints worth of groomed stories at all times. Ensure Epics/Features are reflected accurately for a specific piece of work so that status tracking can be done accurately. Facilitate specific agile ceremonies: o Team Demos o Retros o Daily Standups o Dependency Huddle o Sprint Planning Meetings o Etc. Capture, track and remove team blockers, escalating as needed. Capture, track, and manage funnel and/or initiative specific RAID (risk, agreement, issue, decision) items. Escalate as needed. Note: initiatives that have Project/Program Managers assigned may track their RAID items differently. Capture, track and coordinate dependencies across all funnels related work items (aside from those being managed by a specific Project/Program Manager) in advance of sprints actual start. Ensure backlog health is maintained and ticket refinement ceremonies are consistent and effective (working with the aligned Business Analyst). Update directly or ensure maintenance by others of Jira and Confluence data at all times, ensuring accuracy of data leveraged within the Scrum master dashboard. Leverage the Scrum master dashboard metrics for decision making activities, presenting the information to others as required. Continue to provide feedback and ideas on improving the dashboard and driving a fact-based approach to decision making. Maintain initiative specific timelines and report initiative level status updates as appropriate (aside from those items being managed by a specific Project/Program Manager). Ensure communication occurs with all key stakeholders when sprints are defined (i.e. sprint plans are set). With partner Scrum Masters, maintain master sprint calendar. Manage and maintain the Dependency Huddle and associated before, during and after the meetings as needed. Ensure all funnel specific quarterly planning activities are handled within a timely manner and in a way that ensures the teams can develop, represent and finalize their plans during the QPR cycle. Team Performance/Advocacy: Key advocate for team members as needed and as it relates to sprint work. Safeguard the team and their efforts to ensure delivery health and performance meets expectations without burn out. Maintain a pulse on overall team vibrations, sharing with others as appropriate. Ensure teams processes are being followed, identifying areas where developing individual team members would increase overall team effectiveness. Partner effectively with the Product Manager along with the full team, to ensure successful enrollment occurs across all team members. Delivery Management: Understand and oversee the defined epics assigned to the Team. Account for production support efforts within the Capacity Plans and subsequent Sprint Plans developed with the team. Provide inputs to aligned tech managers of trends or blockers associated with Dev team. Develop and manage milestones and task level activities for selected special projects to ensure visibility and adherence to target schedule. Communicate and engage with key stakeholders, keeping them informed on delivery activities, timelines and blockers. Manage RAID items, escalating to leadership as needed to ensure delivery activities continue as planned. Ensure performance against quarterly plan, escalating blockers or impacts to delivery per plan as needed. Update quarterly plan as required, sharing with key stakeholders when changes occur. Partner with Product Managers on quarterly plan activities, as appropriate. Protect the Sprint, once finalized, negotiating as needed when new items come in at the last minute. In the case of sev 1 production support items, the SM needs to communicate impacts to the shift in capacity mid sprint. Manage unplanned incoming items, ensuring Intake processes are followed as appropriate. Work with the Product Manager, shifting work as needed while ensuring communication or quarterly plans are updated as needed. Draft Quarterly Plan Change Requests as required. Work with Project/Program Managers on resource/work activities as if appropriate. Establish and track team working agreements. Quarterly Planning: Leverage the INTL Quarterly Planning schedule to organize yourself and your Team. This QP planning calendar will help you plan for the right timeframe to schedule your QP pre-planning meetings. Your Teams QP pre-planning meetings should be scheduled 2 weeks ahead of the QP event. Purpose of the pre-planning sessions is for your PdM to introduce Business Epics & Initiatives planned for the upcoming quarter. Your Sr. Engineers will also introduce Tech-specific work for next quarter. Both PdM & Sr. Engineer is responsible for creating a Confluence page for each Epic, which they will use as basis of their introduction and to capture Open Questions by your Team, Dependencies, etc. Both PdM & Sr. Engineer will link the respective Confluence page for each new Epic to your Teams Quarterly Vision Plans page. The # of pre-planning meetings ahead of the QP event may vary between Teams - SM will ask their own Team to confirm what is needed and what works best for them. Normally, the pre-planning meetings are facilitated during the day, Pacific Time, and thus our India team members are not required to join. These calls can be recorded and shared w/ the entire Team. SM + Team will decide best way to ensure that India Team members are kept well informed of what is being introduced during the Pre-planning meetings. Process Improvement (PI): Ensure a continual process improvement focus exists across the team, supporting an environment of experimentation and new practice trials. Ensure consistency with lulus INTL common practices. Contribute to and lead Process Improvement activities as appropriate. Partner with peer Scrum masters to share and leverage lessons learned, fostering a PI culture at all times. Facilitate team assessments, against the common practice frameworks in use for INTL. Team Culture: Celebrate and communicate (peacock it out) team successes including calling out positive team behaviors or individual contributions. Partner closely with the Product Managers and team members to identify opportunities to work closely/collaboratively within the team and across teams. Build time for fun/silly time with the team. Identify and address with individuals or the group those behaviors that run counter to positive team culture. Maintain regular 1:1 contact with each team member. Foster collaborative and productive culture. Foster trust within the team, people speaking up at meetings, etc. -- Keywords: information technology Washington |
| [email protected] View all |
| Mon Feb 19 15:03:00 UTC 2024 |