Many people, even the people supposedly using Agile, have too much work to do. You have project work. You have support work, formal for customer support or sales, and informal for your colleagues. You have reports to write or file, time cards to fill out, or other periodic events. You know your multitasking is slowing down your work, making you crazy, and making it difficult to deliver your best work. You need a way to say no to more work.
An important part of agile leadership is improving communication between people. M. Spayd and M. Hamman are talking about shifting from directive – “managing for results” leadership style to catalysing – “designing environments that create results” style. Lyssa Adkins recommends avoiding asking ”Why don’t you…?” questions when coaching, as being too offensive.
As Agile practitioners, whether you are a developer, tester, scrum master or product owner, we know that it is ALL about communication, right? But how much of what we say and what we hear are words? If, as much as 93% of our communication is non-verbal how can be sure we are ‘saying’ or ‘hearing’ the right thing? Non-Verbal Communication is sometimes referred to as Body Language, but it’s much more than that. This session is designed to give you a gentle introduction to this field. It will help you recognise some common behaviours, and show you how to start using this skill every day.
The first value of the Agile Manifesto is about “individuals and interactions over processes and tools”. Communication is fundamental inside and outside the Scrum team. In his article “Watch Your Words: Feedback Analysis”, Tom Bartel give some hints on how to improve the feedback process especially in a negative context.
‘Agile’ is an incredibly powerful software development methodology, however the word ‘agile’ has become one of those IT buzzwords that people use but do not fully understand.
The Agile Manifesto says that “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation”, but many meetings are a dull waste of time, even for Scrum teams.
Sprint retrospectives are an important tool for Agile software development teams that want to implement continuous improvement and adjustment to their working context. In this article, Jesus Mendez provides some techniques that could help improving the outcome of your Sprint retrospectives.