As a GOAT Conference participant, I need to write better User Stories
That's the most important question to answer. And, did you notice? I specifically didn't do it.
As a GOAT Conference participant, I need to write better User Stories.
What's missing is the "why". That's so important, because writing better User Stories could mean so many things to different people. And if you're going to attend this session, you really ought to know what you're going to get out of it. That's the 'why'.
It's more of an art, than a science. Writing great User Stories, that is.
Why have I been told to use a the funny "As A / I Want / So That" format?
How big is too big, and why should I spend time splitting stories?
Isn't a user story the same as a WBS item?
Good questions, indeed. You likely have more. Excellent.
In this interactive session, we'll explore the fundamentals of writing good user stories. And we'll try to make those good user stories, better. We'll also look at alternatives to user stories, and find ways to represent ideas as product backlog items in other ways. We'll explore why the Card, Conversation, and Confirmation, are so important, and why it's worth the time to INVEST in meaningful stories.
Outline/structure of the Session
We'll cover the fundamentals of User Stories, try writing some of our own, review and improve, and then try again. Then, we'll explore ways to split stories, and finally look at different options to consider.
Understand the role User Stories play, how to structure and form stories, how to split stories, and other options. This is designed to be an intro session to writing effective stories, but participants should not expect to be experts at the end, rather have a few new practical real-world ideas and approaches that can be put into practice right away.
While good for anyone and everyone involved with new product development, this session is specifically targeted to Product Managers, Product Owners, and Team Members - QA Team Members specifically.
schedule Submitted 11 months ago
People who liked this proposal, also liked:
IT has embraced agility ... what about the rest of the business?Jesus MendezScrum Master/Agile CoachSeedbox Technologies
schedule 11 months agoSold Out!
3.5 years ago Seedbox Technologies decided to embrace agile methodologies as its way to develop web based products, get them out faster, survive and thrive competition.
It's all started in a traditional fashion: external consultants were hired to teach employees the agile mindset and how to use agile methodologies like Scrum and Kanban when developing web based products. Project Managers got trained and became Product Owners, experienced Scrum Masters were hired to get development teams to their highest level of performance as fast as they could, developers got trained and developed experience around their team development processes, engineering managers supported agility across the company, and stakeholders directly involved in product development got invited to collaborate with software development teams through agile processes, once they got fully implemented.
That's right, Engineering got agile quite right but by doing so:
- What happen with the rest of the organization?
- What about peoples mindset?
- Is them vs Us or vice versa?
- Are they able to collaborate, inspect and adapt like the engineering teams and people related to agile projects do?
- How do we get everyone in the organization to communicate when we don't share the same vocabulary?
- How do we fill the gap and avoid old management treats get in the way of the companies transition to something bigger than just the teams?
- Shall we wait until they realize that we all need to change or shall we help them get there?
- How do we use are know-how to turn this mess into a big opportunity for the organization to grow?
- Do we need help?
Well, if this experience report gets accepted, I will share what I've learned about:
- The challenges & flaws that we faced when transitioning from team based agility to organizational agility
- Some of my reflections as an inside observer
- How to use the lessons learned as a wake up call
- What can be done to help the organization to thrive
Let's walk together through a nurturing experience report that might ignite your sens and get you inspired to give the extra mille!
Running with the Mob: Extreme collaboration with Mob ProgrammingMike BowlerAgile & Technical Coach/TrainerGargoyle Software Inc.Ellen GroveAgile Coach and TrainerAgile Partnership
schedule 11 months agoSold Out!
Mob programming is collaboration taken to the extreme, eliciting the best from every member of the team. In this session, you will experience the dynamics of mob programming and learn how to use this technique successfully in your own environments.
After mobbing with over two dozen teams, we've seen definite patterns emerge, that we'll discuss here.