Posts Tagged ‘retrospectives’
Monday, May 14th, 2012

What practices can you adopt to help your team experience Agile?
This question was raised by a listener to the podcast we recorded on agile analysis practices with BA coach Yamo. (Find the podcast here.) The specific question that Katie Metcalf asked us was this:
“What Agile techniques would you suggest introducing to a software development team that is currently not using the Agile approach but would like to get a flavor for the methodology?”
Tags: Agile, Agile BA, Agile Business Analysis, Agile Business Analyst, agile requirements, agile team, Analysis Debt, BDD, Business Analyst, business analyst role, Business Rules, Business Value, collaboration, Elicitation, Facilitation, leadership, Personal Development, product needs, Product Partnership, Product stakeholders, Requirements by Example, retrospectives, Scenarios, Specification by Example, Stakeholders, Structured Conversation
Posted in Agile Business Analysis, Agile Business Analyst, Agile Planning, agile requirements, Agile Testing, Analysis, Business Analysis, Business Analyst, Business Value, collaboration, Discovery Workshop, ellen gottesdiener, Learning, mary gorman, Product Partnership, requirements, retrospectives, Scenarios, Specification by Example, Stakeholders, Structured Conversation | No Comments »
Thursday, April 7th, 2011
By Ellen Gottesdiener and Mary Gorman
In September 1977, the TV sitcom Happy Days had über-hip Fonzie, clad in leather jacket and swimshorts, water ski over a shark to prove his mettle—and at that moment even diehard fans knew that the show was past its prime. They were right. After that episode, ratings plummeted, and the expression “Jumping the Shark” was born. When a TV show, or anything else, jumps the shark, you know it’s on its way out.
Our question this month: have any of your software development practices jumped the shark?
For example, are there boundaries around people’s roles? Some organizations tend to confine people to roles such as developer, architect… Continue reading
Tags: Agile, agile team, Business Value, Documentation, leadership, product needs, Product Partnership, Product stakeholders, requirements, retrospectives, Stakeholders
Posted in Agile, Agile Business Analysis, Agile Business Analysis Flow, Agile Business Analyst, agile games, agile manifesto, Business Analysis, Business Value, collaboration, Communication Skills, Documentation, ellen gottesdiener, heavyweight team, leadership, lean, mary gorman, Product Partnership, requirements, retrospectives, roles and responsibilities, Stakeholders, Waste | No Comments »
Friday, July 30th, 2010
By Mary Gorman
In my Stickyminds.com column “Playing at Work: Agile Games Deliver Value” I share game ideas and experiences – the benefits games can provide, selecting an appropriate game, facilitating a game, and designing a winning game.
Designing and Facilitating Agile Games
When writing the column I got to thinking how agile principles could provide a basis for good game design and facilitation. I reflected on a recent experience I had at Deep Agile 2010: Empowering Teams with Agile Games. Working in a small group we created a new game, tested it, and retrospected both the game and our design process in less than half a day. We consciously (and some times unconsciously!) were being agile! (To see and learn more about our game, read Michael Sahota’s summary at The Backlog Is in the Eye of the Beholder.)
Games and The Agile Manifesto
To clearly communicate the agile-ness of our work and what we learned I did a quick mapping to the Manifesto for Agile Software Development. Continue reading
Tags: Agile, Agile Business Analysis, agile manifesto, agile requirements, Agile Workshops, Business Analysis, Business Analysis Training, Business Value, collaboration, Deep Agile, Deep Agile Games, Facilitation, games, Learning, retrospectives, Workshops
Posted in Agile, agile manifesto, Analysis, Business Analysis Training, Business Value, collaboration, Deep Agile Games, Facilitation, games, Learning, mary gorman | No Comments »
Thursday, June 24th, 2010
b
y Mary Gorman and Ellen Gottesdiener
We liked it when a good thing took on a life of its own.
We learned that it really resonated with many folks.
We lacked sharing the full understanding of the technique.
We longed for more sharing.
Liked – Learned – Lacked – Longed For
At the recent Deep Agile event, Mary briefly mentioned a 3Ls’ technique she used in a recent retrospective (Liked, Lacked, Longed For). A few folks tweeted about it, and it took off in the web’o’sphere
To fulfill our longing to share and provide some background, keep reading to learn how we use this technique.
Many moons ago… Continue reading | 8 Comments
Tags: Agile, Agile Planning, Analysis, Business Analysis Training, Business Value, collaboration, Deep Agile Games, Facilitation, Learning, mary gorman, retrospectives
Posted in Agile, Agile Business Analysis, Agile Planning, agile requirements, Agile Workshops, Business Analysis, Business Analysis Training, Business Value, collaboration, Deep Agile, Deep Agile Games, Facilitation, Learning, retrospectives, Workshops | 8 Comments »
Wednesday, March 17th, 2010
What are good practices for delivering a complex product for a broad global customer with a group of volunteers scattered all over the world?
This is a real-world question for me right now: I’ve volunteered to participate on the Agile-BABOK® (Business Analysis Body of Knowledge) addendum effort. Like the BABOK itself, this addendum can impact the practices of a broad worldwide community of professionals.
Learn From Those Who Have Been There Before
Two groups have tackled the problem of using volunteers to deliver an industry standard, so I figured we should “learn before we burn”. One group is the PMI Agile Community of Practice group, and the other is the BABOK Body of Knowledge Committee.
Ideally, learning what worked for these groups, along with their suggestions for what they would do differently were they to do this again, could help the Agile-BABOK addendum effort to start smart: leverage what they’ve found works, avoid or mitigate what didn’t work, and adjust their practices based on their experience. Continue reading | 1 Comment
Tags: agile babok, agile teams, BABOK, Business Analysis, collaboration, iiba babok, retrospective, retrospectives, team retrospectives
Posted in Agile, Agile Business Analysis, Business Analysis, Business Analyst | 1 Comment »