Agile coach, views are my own
Joined March 2009
- Tweets1K
- Following344
- Followers348
- Likes1.1K
Todd Scanlan retweeted
User stories are supposed to be unclear. They're anything from a word to a sentence long with no implementation details. (They describe the user's work, not yours.) They are a reminder to have a conversation just before and during implementation. Fill in the details during Sprint Planning or equivalent—just enough detail to start, not finish. Collect additional details with more conversations as you work. Collecting lots of detail up front is just a waterfall requirements-gathering phase. No agility there.
Todd Scanlan retweeted
I recently talked about User Stories on my YouTube channel, and got asked by several people about how I would deal with "Back End Stories", so here is a thread User stories for "Back End" vs User stories for "Front End"
a #Thread
1/14
Todd Scanlan retweeted
Strategy
⬇️
OKRs
⬇️
Problem statements
⬇️
Solution hypotheses
⬇️
Experiments
⬇️
Evidence
⬇️
Iteration / course correction
⬇️
Agility
⬇️
Customer value
Todd Scanlan retweeted
Your regular reminder that if you are slicing/splitting a user story and end up with 2-x "smaller" stories, each of which must be implemented to satisfy the original story, you are not actually slicing the story, you are doing work breakdown.
Todd Scanlan retweeted
SAFe contains all the other agile frameworks and is therefor the best framework.
#NotMyAgile
Todd Scanlan retweeted
Don’t write your OKRs without involving a UX designer. They are the staunchest advocate for customer behavior goals. jeffgothelf.com/blog/ux-desi…
Todd Scanlan retweeted
For every "could that meeting have been an email?" situation there is a "could that 20-deep email thread have been a 10 minute meeting?" situation.
Todd Scanlan retweeted
Worthy Read: The Mindset That Kills Product Thinking by Jeff Patton (@jeffpatton)
bit.ly/3rDH9yU
#prodmgmt #ux #engineering
ALT An illustration titled "Outcomes" highlighted in yellow, featuring a linear graph showcasing the stages of "Acquisitions," "Activation," "Retention," and "Referral."
Todd Scanlan retweeted
Setting the Stage for the 1st Mobbing Session:
- Start by introducing the concept of Mob Programming
- To help guide the discussion on what it means to work together on one thing, you can walk through these slides: markpearlcoza.github.io/MobP…
@MarkPearlCoZa
trello.com/c/t2eQIKy1/206-co…
Todd Scanlan retweeted
Who is responsible for what in a product trio?
#ContinuousDiscoveryHabits #ProductTrios #prodmgmt #ux #engineers
Todd Scanlan retweeted
Building digital services in sustainable ways is possible… when we recruit, develop, and enable (!!!) digital talent, folks who design/deliver digital products and services.
Lots of progress to share in this space. Learn from 10 lightning talks from 10 A+ people 👏
Register👇
🗓️Join the event Building a Strong #GCDigital Community (DDN2-E22) and learn how digital leaders across the federal government are driving institutional change by developing the digital community across the GC with initiatives. bit.ly/3BustGn
Todd Scanlan retweeted
Worthy Read: Why It’s Easier to Make Decisions for Someone Else by Evan Polman
bit.ly/2TcaMUI
#prodmgmt #ux #engineering
ALT Man painting two arrows: one pointing up, the other curving to the right
Todd Scanlan retweeted
As a Software Development Manager, if you cannot account for 100% of the allocation of your resources, you are a failure.
#NotMyAgile
Todd Scanlan retweeted
As the manager or team lead, make sure you assign all of the tasks to the appropriate individuals at the start of the iteration. It is important that each individual knows what they are accountable for in the iteration.
#NotMyAgile
Todd Scanlan retweeted
Don't start with validation research.
#IdentifyingHiddenAssumptions #ContinuousDiscoveryHabits #prodmgmt #ux #engineering
Todd Scanlan retweeted
Breaking large stories into small ones is a learnable skill. The problem is not that the process is hard, it's that people who have been steeped in an estimation culture & waterfall big-batch thinking have no idea how to approach narrowing or understanding of why it's important.