Tag Archives: Agile

Early Bird and Group Discount tickets on sale

Screen Shot 2016-06-03 at 9.52.54 AM

Gatineau Ottawa Agile Tour 2016 is on November 21st

Early bird and group discounts are now available!

Join us for GOAT 2016 on November 21st, it will be a blast! We thank you for attending the Gatineau Ottawa Agile Tour (GOAT) 2015 last fall, and look forward to seeing you again.

New! You can expect this to be a valuable conference for the 500+ professionals expected to attend the event.

New! The event will be held at the Shaw Centre (55 Colonel By Drive, Ottawa, ON K1N 9J2) on Monday, November 21st. The cost of the event is $95 for early bird and group admission.

To get more information, follow this link:http://www.goagiletou…­

Our full schedule for the day is being built as we speak.

To register to attend the conference using EventBrite, you can follow this link:https://www.eventbrite.com/e/gatineau-ottawa-agile-tour-2016-registration-19710484590­

We look forward to seeing you once again on November 21st for the Gatineau Ottawa Agile Tour 2016!

The Gatineau Ottawa Agile Tour Organizing Committee

La tournée Agile 2016 de Gatineau Ottawa (GOAT 2016) aura lieu le 21 novembre prochain

Des rabais lève-tôt et de groupe sont disponibles dès maintenant!

Participez à GOAT 2016 le 21 novembre, on va s’éclater! Nous vous remercions d’avoir participé à la tournée Agile 2015 et nous espérons vous accueillir de nouveau cette année.

Nouveauté! Attendez-vous à une journée de conférences bien remplie pour plus de 500 professionnels attendus à l’événement.

Nouveauté! L’événement aura lieu au Centre Shaw, 55 Colonel By Drive, Ottawa, ON K1N 9J2, le 21 novembre prochain. Le coût est de 95$ pour les lève-tôt et les groupes.

Pour obtenir de plus amples renseignements sur l’événement, vous pouvez consulter le lien suivant : http://www.goagiletou…­

Jusqu’à présent, l’horaire de la journée est toujours en construction.

Enregistrez-vous dès maintenant!


Nous avons hâte de vous voir de nouveau le 21 novembre à la tournée Agile de Gatineau Ottawa 2016!

Le comité organisateur

Impact Mapping Workshop & Agile 101 – How thin is thin?

We got to try out a new, shiny toy for our session today. It’s the latest product from Nureva called SPAN. A great tool for ideation and collaboration.


Here is a closeup of our working session.




Impact Mapping: Making a big impact with software products and projects


Lean Coffee @ Agile Ottawa

Last night I facilitated our first Lean Coffee meetup at Agile Ottawa. Thanks again to all who made it out, and to You.i TV for the venue, food & drinks! 🙂

We covered a lot of interesting topics:

  • How to sell executive sponsors on addressing technical debt?
  • How to transition slow adopters from waterfall to agile when others have moved on?
  • Wardley Maps – how they can be used to decide when to do Agile.
  • How to estimate user stories?
  • How to engage an overloaded Product Owner more with the team?
  • Adopting [agile] with non-agile clients.
  • Scrum & Continuous Delivery – are they compatible?

See the pictures below for key points covered.

We also had some great feedback on the session:

  • Interesting discussions (x6!)
  • Loved it, do it again (x4!)
  • Well moderated (aside: thanks! 🙂 )
  • Got a lot of good ideas

I’m already looking forward to our next Lean Coffee 🙂

Here are the pictures I took of our whiteboard:

Lean Coffee 2015-12-08Lean Coffee 2015-12-08








Lean Coffee 2015-12-08


Lean Coffee 2015-12-08

Lean Coffee 2015-12-08



















(note: cross-posted, original: blog.spurkis.org/11606.html)

Gatineau-Ottawa Agile Tour 2015 schedule confirmed!

(voir la version française plus bas)

Hi all!

The Gatineau-Ottawa Agile Tour 2015 program has been confirmed!

We’ll have 2 great keynotes from Richard Sheridan and Gil Broza, as well as 4 tracks of 4 sessions each, with a variety of workshops, experience reports, and talks aimed at all levels from beginner to advanced. That’s a total of 16 sessions to choose from!

To see what we’ve got lined up for you, visit:

Visitez goagiletour.ca
Lundi le 23 novembre
95$ pour l’admission générale
75$ par personne pour les inscriptions en groupe
30$ pour étudiants

There’ll be many experienced agile practitioners to talk to outside of the sessions, so it’s also a great place to bring your questions!

Hope to see you there!

Agile Ottawa


Chers amis et collègues !

L’horaire de la tournée Agile Gatineau Ottawa 2015 est maintenant finalisée !

Vous pourrez assister aux présentations de nos deux conférenciers principaux : Richard Sheridan et Gil Broza. Il y aura aussi 16 présentations incluant des, ateliers, retours d’expérience et discussions pour tous les niveaux.

Visitez goagiletour.ca
Lundi le 23 novembre
95$ pour l’admission générale
75$ par personne pour les inscriptions en groupe
30$ pour étudiants

Il y aura aussi plusieurs praticiens Agile séniors disponibles pour répondre à vos questions sur place.

En espérant vous y voir!

Agile Ottawa

Secrets of Agile Success – Minutes From Our “Success Faire”

Once again, the Agile Ottawa community did not disappoint… The evening started with an engaging session on Core Protocols, facilitated by our own Ellen Grove.  Ellen covered the basics of Core Protocols and lead a very effective exercise where the group had the chance to try out the protocols on each other.

In the spirit of this, we moved on to exercising one of these protocols in more detail… the “Brag Protocol”.  Participants shared stories of Agile success, we promptly applauded and cheered on…  and we attempted to capture the source of these successful stories.

Without further ado… here are a few secrets for achieving Agile success captured from our meetup:

1. Allow the team to express their opinions in anonymity to help reveal the truth.

2. Bring a ball to standup. Rather than “follow order” throw the ball around to choose who speaks next… this can lead to interesting conversations and new interactions.

3. Need people to take the lead? As the team for volunteers, you’ll discover that (given the opportunity) people WILL step forward.

4. The antidote to despair on a project is empowerment. Start fixing problems.

5. If you keep sharing Agile stories and lessons with the team; over time, you will find that you are transforming people in great ways that you didn’t anticipate.

6. Formulating the project “requirements” as “problems”, allows creative ideas to come forth and empowers the team.

7. Mob programming is a great way to “gel” a new team together and build Agile skills. It’s also an effective way to solve problems.

8. Creating a safe place to work allows the team to make mistakes and grow.

9. Looking at a laundry list of a backlog? Turn that list sideways and narrow it down to the most important stories.  Creating a reasonable scope of work means more work gets done… and less time is spent talking about it.

10. Transforming a team’s physical space (e.g. take down those walls) creates opportunities for the team to share and work in new and more effective ways.

11. Create opportunities for teams to share their different experiences with each other… being able to visualize work is key to making this happen on a regular basis.

12. Confront those monsters! Often problems that appear impossible or extremely hard to fix can be resolved quickly by working openly and collaboratively.

Thank you to all who participated and shared their experiences with the group.

Lessons Learned From Our “Fail Faire”

“What an amazing evening!”, “The best Agile Ottawa event I’ve been to”, “This was great!”

These are only a few of the positive comments from the group that came together to share their failures. Anyone who wanted, which was almost everyone, got up in turn and told a story of mishap. These were not stories of greatness or accomplishment. There was no bragging or boasting. People told real stories about themselves where they did the wrong thing.

The wonderful part was what they learned from that experience. The sharing was part healing and part teaching. It would be impossible to try to recreate that evening (you really had to be there) but we have captured some lessons learned to share with the community.  I encourage anyone who was there to add their comments. 

Lessons Learned

1. Have facilitation techniques ready for talking about tough problems.
2. How you implement change is as important as the change itself. If
you mandate it – you must also be a part of it! Additional: Technical
practices are important (not optional).
3. If it isn’t Agile – call it!  Training is important for team alignment.
4. Pay attention to the parts of the system that are hard to change.
That’s where the volatility will be in your project.
5. The team must commit to at least 1 hour a day when the whole team can meet.
6. Beware of “sunk cost” – make sure your project still has value no
matter how far into it your are…
7. Don’t let process distract you away from people (e.g. creating
collaboration or a shared understanding).
8. Make sure you have a Product Owner.  An absent Product Owner is the
first sign of trouble. When in a large organization ensure that you
actually have executive buy-in as well.
9. When investing in change, ensure that you have change management in
place.  Again, ensure executive buy-in first… they also need to be
educated on change.
10. Be honest with yourself – personal retros are a very good thing.
Sometimes, you are the one who needs to change.
11. Your backlog isn’t a Christmas list. Sorry, Virginia, there is no
Santa Claus.
12. Prioritize your backlog in advance. Not all decisions need a
meeting (necessarily) – explore non-verbal prioritization.
13. Agile projects need self-organization… and not everyone
necessarily wants to self-organize.  You need buy-in from the team.
14. Don’t abandon an agreed upon practice unless you know why.
15. People need time to absorb change… they need to know the value
of the change and they need to have confidence in their own capability
for change.
16. Month long Sprints are risky.  Shorter Sprints are good for
feedback and learning and ensuring that the team is meeting
17. Again, know your Product Owner and make sure that they are
empowered to make decisions.
18. “Cracking the whip” is a poor motivational technique.
19.  Follow-up with your team after teaching them something new.
Teaching is the “beginning of a journey”.
20. Question: How to get devs to meet / read acceptance criteria?
Idea: To achieve acceptance / commitment to deliver, ensure that all
stakeholder are on board (not just PO, BAs…  but dev and testing
too) in creating the acceptance criteria.
21. Code review. Code review. Code review. No one person is
infallible. The more the merrier… “To go fast, go alone. To go far,
go together.”

February Meetup: Introducing Agile to an Organization

The meetup for February is still on. We will be having a panel discussion on “Introducing Agile to an Organization”. We have 3 panelists lined up — with small company, large company, and contracting experience in Agile.

It’s going to be an interesting event this month! See you all there.

February 24 Event

We are actively planning the February event where the topic for the evening is “How to Introduce Agile to an Organization”. The plan is to have a panel and a number of preset questions. Following the questions there will be an open Q&A / discussion with the group.

Here is the challenge: we need four panelists and so far I can only tentatively confirm one. Drop me an email if you know of someone who would be interesting in being on the panel.

See you all soon.

First Agile Ottawa Meetup of the New Year…

… is on! As previously discussed the topic for the meetup is Agile Tools. With that in mind I am happy to announce that we have a presenter for this session. Ian Kent will present on the Agile Development/Collaboration environment that he was responsible for setting up at Nortel Networks. Continue reading