Month: February 2013

SCRUM – Becoming agile – another book

I picked up another book on SCRUM by the same authors as I read and wrote about in this post. I finished “The Elements of Scrum” which is a more thorough exploration of the SCRUM framework. At work we have other departments that follow the SCRUM framework and have a great results. We are moving my group now towards the framework and I am working on implementing our structure of the framework. One of my key take aways from the book is below. Collaboration between business people and developers should be like voting in Chicago: do it early and do it often! I have been in the software development industry for well over 15 years now and have been involved i so many aspects of technology. I have seen many many projects slip and complete late and above budget. I have been good at enforcing our timelines in the past, which to be fear means you have to control scope creep. But you also have to have a team that is committed and dedicated to the project. I think this is where SCRUM and agile comes in and helps to make a difference. A team is a group of skilled individuals functioning in sync to achieve a common goal. I am moving our team to more of a agile scrum-based structured which is easy in the organization that I work because many...

Read More

SCRUM – Becoming agile

I have been gaining a better understanding of SCRUM lately and read the book “Scrum: a Breathtakingly Brief and Agile Introduction” and just loved the book. After reading through this short and concise book in a day I decided to purchase the more thorough “The Elements of SCRUM” by the same authors. I read many of my books on the Kindle App on my iPad, it is convenient for me to carry around and I have a library of books at my finger tips. But, I can highlight and take notes on the book as I read it and they are available online. My highlights for this book at available and public for all to read. All features should be put together in a phrase formatted as shown below. As a <type of user>, I want to <do something>, so that <some value is created>. A big take away for me from this book, there are actually many items that I took away but this one really stood out. At the end of your sprint, you will be demonstrating working software or thy name is Mud. Each sprint should have working software, my biggest question on this is what about early on in the project? I have many early sprints have a deliverable of documentation or other items that are common to the early part of the project. I wanted...

Read More