Author Archives: Lidia Rojco

Honesty and Openness for Agile Team – Meet Up

“Are you telling enough truth?” or, “Honesty & Openness for Agile Teams”  Honesty was the main topic of the May Meetup session for the Ottawa Agile Community. Amanda Holtstrom presented tips for maintaining openness in teams and encouraged participants to experiment with these practices in their own groups. (here is the Presentation)

“Openness” is one of the key values set and manifested by any Agile Team.  Openness to feedback, openness to recognize any issue, openness to accept changes, and openness to keep improving! This is a quality which helps Agile teams to always move forward and achieve their desired results. Indeed, openness is an important value for Agile teams to commit to!

To be honest within an Agile team is a core communication need and key to the overall work process. Honesty contributes to the overall Transparency of what you’re doing as a team, and helps you proceed with a fair process and good result (Inspection), as well as ensures equitable Adjustment.

Transparency, Inspection, Adaptation – Agile way of process organization which has some similar conceptual bases with Empiricism – by notion: Empirical evidence is the knowledge or source of knowledge acquired by means of the senses, particularly by observation and experimentation.

The idea of empiricism applied to Agile values was presented by Simon Bourk. While we all agree on Agile Values it is important to think and try to prevent potential problems that might cause the failure of any team: Absence of Trust, Fear of Conflict, Lack of Commitment, Avoidance of Accountability, and Inattention to Results. (see Pyramid image presented by Simon)

To overcome failure and find improvement requires team members to be honest, and communicate that honesty in a productive way. Giving a feedback is an invaluable tool: it can be immediate or retrospective, and can come in may different forms. Whichever style you use, whether positive or negative feedback, it should always be given in a way which is constructive to improving the team. In my own experience, helpful feedback focuses on the cause and effect of a situation, provides suggestions for improvement, and motivates and encourages the person to do better going forward.

Amanda closed the meetup with a presentation of tactics for efficient communication, and suggestions   for coming to agreements when there is disharmony among team members. Following the presentation, we had an interactive discussion between participants.

The only way to come to a consensus on any issue is the tolerance of different opinions and, when faced with disagreement, keeping attentive of your opponent. It is just as important to have a fair perception that your opponent also tries to find and present his way to change something in order to improve something. Understand that you both have the same target: it’s just a matter of how to get there. Recognize and acknowledge each other’s arguments, and work to consolidate them to reach a mutually agreeable solution.

Honesty and communication are the keys of success; the breakdown of either are often the cause of failure. At our June Agile Ottawa Meetup session we will continue to explore real-life examples of failure and experiment with ways which lead Agile teams to success.  I kindly invite you 🙂  to June session dedicated to Pitfalls and Successes of Self-Organizing Teams.



Amanda presents Communication Tactics


Simon presents the Empiricism




Why or Why Not Agile? – Meet Up


“Sorry, the new Champlain Bridge cannot be built using Agile…” – Mathieu Boivert presentation attracts many participants at Agile Ottawa MeetUp!

This MeetUp brought together Agile practitioners and students who have just begun a journey in Agile. The topic of presentation provoked an open and interactive discussion on the topic, “Is Agile recommended for every project?”

Some follow up questions included, “What should we take into consideration when proposing Agile, and once it is decided on, how do we organize and implement it?”, “Why Agile? “, and “Why or why not Waterfall?” Everyone was encouraged to come up with a real example, and arguments and ideas based on their own experience and practices.

The values and principles of understanding Agile provide a base to identify potential the type of project which can be successfully implemented using this approach.

Agile Manifesto was a dedicated theme for the MeetUp introduction session moderated by Simon Bourk. The consensus reached through open discussion between participants was very useful to underlining the Agile Values applied in practice, and facilitated answering the question, “Why or why not Agile?”  for any project.

Indeed, Agile is essentially developing an asset by doing your product step by step, from sprint to sprint, from delivery to delivery! It also means starting the project and asking, “How aware are we of requirements, technology, client expectations and team maturity?”  It is essential to assess and evaluate Known and Unknown zones (see Stacey’s Chart), as well as acceptable levels of Uncertainty we can afford upon our project. This evaluation will help you decide on your approach to project implementation and efficient risk mitigation.

Delivery Value vs. Delivery on Scope – You Decide!

Agile Ottawa MeetUp was a great opportunity to meet members of the Agile community and exchange ideas, and gain knowledge through hands-on practice!

Simon and Mathieu created a very pleasant and friendly discussion environment. The interaction and dialog between presenters and participants was key to creating a positive and efficient atmosphere – and a lot of smiles!

 MeetUp – Meet people!

I appreciate the opportunity to get to know new people, participate in open discussion, share experience by interacting with others, and am looking forward to the upcoming MeetUp!

Next time, we’ll have a new topic, new ideas, and a new exchange of knowledge and experience! Everyone is welcome! 😊