Hello again from the Project Management Team at Cake and BAMTECH Media. Welcome to this, our sixty first edition of “This Week in #Agile”. Please feel free to peruse some of the articles that we’ve enjoyed reading over the past week.
“Why you need a Change Management Strategy” created by Prosci read by Marc Nevins
This is quite an interesting (and recent) article that highlights the “must haves” when organising change within an organisation. It does echo Kotter's 8 Step Change model, (which is no bad thing), but it also includes links to more contemporary information regarding the subject, including the various components of Change Management Plans, which readers might find helpful.
“5 Signs Agile Team Roles Might be Falling Behind” created by The Agile Times read by Sarah Clarke-Nevett
This articles describes 5 distinct signs to look out for, in order to assess if your team are likely to underperform in the long run.
“Five Lessons I’m Thankful I Learned in my Agile Career” created by Mike Cohn read by Darren Halket
In the context of learning and improvement Mike covers five interesting topics including
how the right way may seem more time-consuming and difficult but more worthwhile, confronting the people challenges within a team and managing stakeholder ex
“Beware Haloes & Courtesy Copies” created by Joe Wynne read by James Furness (Login Required)
As a project manager, managing people is a large component of your work. So it's worth Think about how you learn the techniques you use. Do some come from experience? From books, seminars or training courses? Did you learn some from watching others? Do you do things because everyone else does them?
“I wish I had me when I was you...” created by Laura Barnard read by James Furness (Login Required)
Have you ever heard a stakeholder on your project say, “I’m completing the template you guys asked me to complete?” Or maybe you’ve heard, “I’m completing the steps in your process.”
“THE STATE OF SCRUM REPORT” created by Scrum Alliance read by Jonathan Orgel
More than 20 pages on the state of scrum. Too much? Scan through it you will find some data that fascinates you. Or perhaps more important solid data to support for a proposal.
“Myth 4: In Scrum, the Product Backlog has to consist out of User Stories” created by Barry Overeem read by Jonathan Orgel
The product backlog lists all the work that is deemed necessary for the product. How Scrum Teams decide to capture this work is entirely up to them. They can write User Stories, they can use a bunch of keywords, write use cases or even draw pictures.
Here at Cake we love catching up with people's opinions and articles, so please do not hesitate to get in touch if you have something to share. You can contact us via email on email@example.com or on twitter @JonathanOrgel
Many thanks to Barry Overeem for this week’s image.