David Paul McQuiggin
[Remote] .NET Lead Engineer | Solution Architect | CTO | Azure | Data | AI
Follow me
March 10, 2021
I had an interesting conversation today with a colleague whose opinion I value, and it was yet another of those conversations that centres around the topic of frustration with Scrum.
It's a topic that has maybe be done to death amongst bloggers and industry names, and I won't rehash the usual arguements along the lines of 'you are not doing Scrum right', 'what does Agile mean to you' etc.
Instead I will simply put a summary here of what I said to my colleague; when I was co-founder of a small company with large clients, I had the luxury of setting our own internal processes in a small team (c7 devs), while also having the need to report on progress to clients that were used to working in a pretty formal manner.
What I found worked, for our little band, was this:
1. Don't meet in the morning to discuss what you will do that day.
2. Meet at the end of the day to discuss progress - what was achieved, what might take longer, what you plan to do tomorrow.
3. Start the next day without a meeting, but knowing what you need to do, in your own way.
4. Don't wait for the meeting to raise your hand if you are stuck / blocked - talk to the team naturally. If you need more information from the client, let me know, and we'll call them together.
March 10, 2021