Think about your Agile environment. Have you implemented your version of Agile and stopped there, content that you're done? Have you focused on what Agile is actually about?
In this blog post I'll share my views on what Agile is, and more importantly, what Agile isn't.
If your business interacts with people, then you’re trying to serve their need - you’re acting in service. Applying the practices of Service Design could help your organisation.
Taking on the role of Product Owner is no small feat, ensuring a balanced view of commercial needs, user needs and technical feasibility.
Ensuring the organisation is setup to allow the Product Owner to excel, giving them the responsibility and autonomy, yet support they need is crucial.
This week we held our bi-montly offsite, providing a great opportunity for us to regroup, reflect, reward and focus. The format for our offsite varies, such as hackdays, reflecting and planning, refresh OKRs and guest speakers.
Today Web Directions launched Transform 2017, Australia’s Digital Government Conference, to be held in Canberra late March.
I’m excited to be representing Pragmateam's transformation experiences in two parts.
Mid 2016 we found that people were regularly bringing this objective to life, whether it be experimenting with new techniques, organising a learning lunch, presenting at meetups, all with a positive impact on the rest of the team. But we were lacking a way to naturally yet formally thank, reward and recognise each other.
The “team” in Pragmateam is critical to us and our culture. We are a collective of like-minded practitioners who are all inquisitive, continually looking to experiment and learn. And we acknowledge that working together as a team will get better results for us personally, our clients and their customers.
Learning and sharing is a key ingredient within Pragmateam’s culture. While we have a very healthy internal shareback rhythm (more about this later) we also actively seek ways to give back to the community, sharing our techniques, experiments and learnings.
September marked the 2 year anniversary of Pragmateam. It felt timely to reflect.
While I wouldn’t say every day over the last 2 years has been smooth sailing (we would be bored, unhappy and missing a lot of great lessons for life if it were), as company directors there are a few key principles Juliano and I have subconsciously adopted which I believe have assisted us to stay on course.
In the spirit of continuous improvement, we should always be actively seeking feedback, opportunities to do better next time.
At Pragmateam we believe in learning and improving so much so that we have captured a number of OKRs around learning culture, one specifically regarding meetings, workshops and sessions.
Sprint Planning is one of the well-known “ceremonies” within the Scrum framework. While at Pragmateam we absolutely see the value in planning, we typically approach Sprint Planning from a perspective of flow. The question we want to answer during sprint planning: How do we use the weekly/fortnightly conversation to continue the momentum of the previous sprint?
Delivery-orientated coaching means showing things rather than talking about them. Coaching a team in 'advisory mode' (ie. not being hands-on in delivery) is a difficult and long path to proper agile delivery. If the team hasn’t seen what ‘good agile’ looks like, how would they know where they are heading? Hands-off advice from a coach doesn't usually help.