An Excellent Book – The One Minute Manager

I just completed reading "The One Minute Manager Anniversary Edition". I have gone through several books and trainings on working with people to deliver a common goal. By far, this book has captured the concept to its best in layman’s language.

The One Minute Manager is a concise, easily read story that reveals three very practical secrets: One Minute Goals, One Minute Praisings, and One Minute Reprimands.



A good book – Agile Project Management with Scrum

I am reading a neat book from MS Press. It is called ‘Agile Project Management with Scrum‘. The book was published in 2004. It talks in detail with a number of case studies. So everyone understands the principles of SCRUM. If you want to learn the practical side of SCRUM, I strongly recommend this book.
The theory and practice of SCRUM is very appealing. If you would like to know more about Agile Development, learning about SCRUM is important. As I read through the book, I realize that I have practiced many parts of SCRUM in many of my past projects. Cool!
The definition of SCRUM from is below:

Scrum is an iterative, incremental process for developing any product or managing any work. It produces a potentially shippable set of functionality at the end of every iteration. It’s attributes are:

  • Scrum is an agile process to manage and control development work.
  • Scrum is a wrapper for existing engineering practices.
  • Scrum is a team-based approach to iteratively, incrementally develop systems and products when requirements are rapidly changing
  • Scrum is a process that controls the chaos of conflicting interests and needs.
  • Scrum is a way to improve communications and maximize co-operation.
  • Scrum is a way to detect and cause the removal of anything that gets in the way of developing and delivering products.
  • Scrum is a way to maximize productivity.
  • Scrum is scalable from single projects to entire organizations. Scrum has controlled and organized development and implementation for multiple interrelated products and projects with over a thousand developers and implementers.

For those who do not have time to read an entire book, here is a link to concise explanation of SCRUM process.

Added o June 7th

The responsibilities of the ScrumMasters are summarized below:

  • Remove the barriers between development and the Product Owner so that the Product Owner directly drives development

  • Teach the Product Owner how to maximize ROI and meet his or her objectives through Scrum

  • Improve the lives of the development team by facilitating creativity and empowerment

  • Improve the productivity of the development team in any way possible

  • Improve the engineering practices and tools so that each increment of functionality is potentially shippable

  • Keep information about the team’s progress up-to-date and visible to all parties

Continuous Integration, TDD, and NUnit

I lacked in-depth knowledge on NUnit, XP, and Continuous Integration techniques. Having spent nearly a day on it, now I am much more familiar with these concepts and its technologies.
Here is a good article on Continous Integration in simple English. I faced portions of this concept in one of my earlier projects. If I were to take this route, I would do it properly.
Some articles on Test Driven development
Avanade’s knowlege base has a wealth of information on practical use of these concepts. As in any organization, this information is internal to its employees.