Comments
Stephen,
Hubert is dead on, so are you. Note that our release commitments on Agile Commons are at the epic level and we routinely do not publicly commit to everything in our backlog. We have not missed a release commitment in over two years. With that kind of visibility and predictability, the need to share details disappears. It is the process of building trust.
The only bummer is that trust takes time to build and requires a give and take in the short term. My recommendation is undercommit and over-deliver for the next two releases, but do this 1/2 way to your next public release date and on the actual release date.
Does that help?
Ryan
Agustin,
I will take a quick stab at this, but others may add on.
1. We use lean as an overarching model to put learning first and put a set-based model on our architectural and portfolio management governance. We do not use RUP phases and only use two real stage gates - kick-off and production.
2. We use vanilla Scrum to run our four product lines with five scrum teams distributed in Colorado, NC and India. Scrum is a great project management model, but it says nothing about engineering practices or portfolio practices.
3. We use all the XP engineering practices with some teams exclusively pairing and some teams pairing as needed with code reviews.
Traci,
It is common for us to do our iteration work back to back. Those meetings go fast for mature teams - two hours for the combined effort of retrospective and planning. We do a company demo for all teams every two week. That meeting runs on Fridays with a focus of sharing and stays decouple from team by team retro and interation planning.
On highly dependant teams with locked schedules, that demo meeting is critical to happen before your next iteration planning meeting.
For Release kickoff, planning, and retrospective, that is a wholely different. We tend to do the retrospective and kick-off the day prior to release planning. Release planning with four product lines in break outs tend to take about 3 to 4 hours and that is about as much meeting time as most of us can handle. We typically have lunch together in the middle of that process. Some of the lunches get a bit wild, based on a the last release; afternoon planning can fade badly:)
I sure hope that helps?
Ryan
This was a great presentation and format. I would highly recommend this for folks trying to understand the changes we need in the way we live. The facilitation was great and made the event very actionable. Our event had about 55 folks and 7 local groups to help you channel your next step actions. Please see the web site above to find other showings of this in Boulder or your local community.
Mike, on the landing page there is a small piece of text that says the promotion code is RELEASEMYTH.
Thanks tons to the folks at Luminous Recycling in Denver. They recycled all our old stuff here locally. As a result, we did not export our probleme or opportunity to Gana ro China. You can find Carl Schachter at 303-660-2000 www.luminousrecycling.com.
Dale and Jesse - Great work!
How many pounds did we end up recycling??
If you are looking for a copy of the slides. I attached a PDF to this comment. Please feel free to ask more questions in this forum.
FlowPullInnovate_808_Webinar.pdf (5.9MB)for more on the BMC story and for a comprehensive treatment of scaling agility based on real world experiences, check out Dean Leffingwell’s book and Blog: Scaling Software Agility: Best Practices for Large Enterprises. You might also join in some discussion in the Enterprise Rollout Topic area here in Agile Commons
- MIke,
Actually our manta statement headed toward two statements:
- Sharing the passion to Continuously improve the Art of Software Delivery
- Short form - Share the Passion to Deliver software better everyday
- A European Conference of 500 by 2010
- Deliver a corporate program that is funded
- $300K or more profit from Agile 200X conference
Based on four Key Thrusts:
- Research and validate European and Corporate program
- Sell corporate program/services for funding opportunities
- Deliver a funded corporate program
- Run 2 programs around Agile and organizational change
- Incrementally invest in story/experience repository
Ryan
