<img height="1" width="1" src="https://www.facebook.com/tr?id=&amp;ev=PageView &amp;noscript=1">

This Week In #Agile 1/12/2017

Posted by Jonathan Orgel on 01/12/17 13:40

Hello again from LoansWithNoCreditCheck and our Project Management Team. Welcome to this, our sixty second edition of “This Week in #Agile”. Please feel free to peruse some of the articles that we’ve enjoyed reading over the past week.

created by and  read by

The latest version of the scrum guide. See and   for comments on the changes.

created by  read by

Tim’s article covers the pitfalls of implementing organisational change, with him highlighting the need for a healthy change management strategy, the requirement for the organisation undergoing the change to provide proper consideration and engagement of people involved in that change (for both micro and macro environments - at all levels), and the need to ensure that an effective communication plan is in place. The latter, he argues, is fundamental to the success of the whole change initiative.

Like many other authors of this topic, Tim references the omnipresent Dr John Kotter’s “8-steps” and Kubler’s “S” curve when highlighting the importance of people and change, and also the need for effective communication. For the more interested reader, there are a few helpful additional links contained within Tim’s article too.

created by read by

While the practice of agile requires a “Caves and Common” setup of teams, there is a reason for it. Mainly, it’s to make sure communication is ongoing and regular. This requires a specific setup of office equipment and overall layout within the workplace. The “Caves” aspect refers to a place where some team members have the occasional place or space to work alone for a short or brief period of time, while “Common” is the area where most team members spend their time with the rest of their team for the majority of time in their day.

created by read by

There are many ways to conduct a Sprint Retrospective and there are plenty of guides out there to help. I personally favour number one in this article, where Pablo talks about “GET A DIFFERENT SCRUM RETROSPECTIVE EVERY TIME”, after reading this article I will be trying number two & three in my own up and coming project Retrospectives.

created by  read by

The sprint review meeting is maybe the most important Scrum event for product people—it helps you collect feedback and make the right product decisions thereby increasing the chances of creating a successful product. Product owners are not always clear on who should attend the meeting, how it should be run, and how to collect the relevant feedback. This article answers these questions and includes tips for getting the most out of the sprint review.

created by  read by

Bloat takes place when you retain stories in your backlog that are either less important, unnecessary alternatives to other stories or stories of low priority. Retaining every possible story for building the product weighs down the backlog while squeezing (or obscuring) the highest-value stories.

Here at LoansWithNoCreditCheck 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 protected] or on twitter

Many thanks to GE CEO (quoted by Jurgen De Smet on LinkedIn) for this week’s image.

GE CEO Quote.png

Recent Posts

Posts by Topic

see all

Subscribe to Email Updates