mozmeao / agile-task-force Goto Github PK

Description

I would like metrics on how many tasks my team completes and how many carry over in a sprint.

Additional Information

Ugh taiga wont give me pretty metrics!! See screenshot

Sort out where this lives.

• Easy to edit.
• Change log

Description

Populate definitions (and add any new ones) on our glossary.

Additional Information

Ones to pay particular attention too:

• User story
• Epic
• Sprint
• t shaped
• project
• scope
  -- product
  -- project

Blog? Email Updates?

sfasdfasdf

• do thing #1

Description

Based on AgencyAgile training update how we do sprint planning/backlog grooming and maintenance.

Description

We need a service to:

• gather and store data about issues (date created, date closed, etc.)
• provide deeper reporting for lead and cycle times for each issue

Additional Information

[List of possible solutions/services to be provided here for further analysis]

Description

We have a good full day to cover operational topics. Depending on what gets covered we want to capture best practices. Initial thoughts are:

• Running better standups.
• Retrospectives.
• Structuring the day.
• Inter-team dependency handling.
• Scrum Board/Kanban Tools & usage

As this week progresses please add topics you think we should cover on Friday. @MaciekPluta @JennyDouglas @JenniferHB @andrewzyga

Some Ideas We Are Kicking Around

• Running Context Briefing Remotely
• Developing Roadmap Remotely
• Working with team leads or folks requesting projects who have not gone through training - PMM, and folks outside of marketing
• https://mural.co/
• Running Better Standups
• Sprint Planning
• Retrospectives
• Scrum Board / Kanban Design
• Critical Success Metrics
• discuss how to optimize project planning virtually - 7 sheets
• How to virtually show card roadmap - jenny has an idea, may not work
• what to do about non-durable resources? is it create a process to get them assigned before the project planning? or does the team go through the planning and then we get resources? does this mean we need to have full creative briefs (for creative resource needs) or full project briefs (moz.org)? Yes and note Jenny B's team ..most of this team don't implement the actual work
• Since leadership is not participating, how do we get them to reconcile having messy representation of project plans (7 sheets/card roadmap) vs. 50 page decks?
• Managing up: what this looks like -- how we want them to participate. (JB)

Notes from training

1. Usage stats from gh / trello

We think it would be beneficial to have some number of metrics that we can look at to gauge the effectiveness of our Agile system and to be able to measure the impact of the Agile Task Force.

Notes from Ben & Alex Brainstorm

Durable Team Board

• Cycle Time & Lead Time: Predictability
• Non-Kanban: Stories over time.
• Usage: Is it helping the team.

Backlog

• Size over time -- noodle

User Stories

• Level of comfort.
• Qualitative understandability by team.
• Sized and specific enough.
• Completed work matches user story/fulfills user story. (Quality of acceptance criteria).

Daily Standup

• Completed on time
• Attendance
• What makes a productive standup.
• Why is this perceived as not important for some folks.
• Blockers.
• Rotate who runs this?

3 Week Sprints

• Research this one a bit more.

Sprint Planning

• Prioritization etc.
• How efficient(define this) is this long process.

Thoughts From Training

• Document Waste (Cruft)
• Things used on a daily basis (documents / tools etc)
• Number of meetings

Description

Integrate learnings from AgileAgency around estimation into our documentation.

Description

Post training we want to develop onboarding materials for new & future team leads.

Additional Information

Rough Draft Of Things To Cover

• Outline of team lead responsibilities.
• Team lead role during various phases of projects and planning.
• Things from agileagency training.
• Relationship between sponsor and team lead

Update readme:

• mission statement
• team
• advisors

Description

Based on AgileAgency training we should develop a set of best practices around how teams should roadmap their work.

Develop a plan for recapping sprint plans for senior leadership. This shall include:

1. Creating a common format or template for each durable team.
2. Deciding on delivery method, emailing out, linking too or some combination.
3. Sorting who should be on the recipient list.
4. Socializing with team leads that this is a task for them.. and holding them to do it.

Background Info

Original Email Note From Mary Ellen

I find that sprint planning recaps are a super helpful way to get an overview of a team’s priorities, provide an ability to create connections between durable teams, and keep functional team leaders as with other stakeholders throughout the org in the loop as well . I regularly meet with the team leads who Janis works with so they can share their sprint priorities, and if we can’t do it in person, they send an email (Dan Brown’s below is a great example). I also noticed that Kirby pulled together a fairly high level sprint overview that was shared in Focus on Firefox last week. Seems like this could be a great overview to standardize and share throughout Marketing. Is that something you think the PMs could lead — collating their sprint overviews into one doc?

• Example Emailed Format From Dan Brown
• Example Overview Slide From Kirby

Description

We've collected some questions around the advocate role:

• What are this persons roles & responsibilities?
• What is the lifecycle of an advocate?
  • How do they get assigned to a team?
  • How do we remove them from a team/move them to a new team?
• Can I make an advocate order me a pizza?

• Create the document and share with the team to fill in

Planning what we do the after training, the week after, the next months.

• Document what we want to develop after the training.

• Draft survey

Description

Should demos be promoted to a ritual... the thinking here is that if cross-marketing demos are important and we want to invest in them.. perhaps they become a ritual