For a few new hires, you might need to do some training and have some discussion on an expected behavior for a Scrum team member. Sometimes, for a few devs, it will come naturally. For some others, you might need a longer training.
If you are working for a big (or even a medium) company, you have been attending several times directors presentations.
Big news today!
The agile manifesto states: “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.” I would say that it is true for 99.99943% of the situations…
Maybe a first comic of a series on the same topic. Agility audit checklist #1.
For those completing some forms over the web…
I guess some of you has experienced these unpleasant situations recently.
Have you ever heard of the coding/management approach called : HDD? Here is what can happen if your team try it.
A true story I witnessed last year.
Communication is key inside a Scrum team. And nowadays, communication is a cross-channels activity.
Retrospective is one of the most important event during a Sprint. Scrum opens up a quick feedback with the customer, but also, it opens up quickly a feedback loop within the Scrum team and the way they organize their work and collaboration. Sometimes, weird stuff is proposed out of these retrospective sessions.
I often get this question from developers worried to try Scrum: “Who will decide if we get into a conflict?” Clearing up the traditional team hierarchy seems to scare a few people who were used to have control over the team’s decisions.
Here is a special edition of Scrum Comics for the Microsoft BUILD 2013 keynote presentation.
Phones. We can’t live without them. They are part of : personal life, professional life, couple life, bored moments life. However, sometimes, you wish you could live without it.
Changing is not always a good thing. Most of the times, a change is needed. However, forced changes can sometimes decrease an organization/team efficiency.
