Agile Project Management

You might be interested to know I did a couple of posts on project management & PRINCE2 which cover project management in a more general way & that's at
http://claireabella29.com
The book I read to research this post was Agile Project Management for Dummies which is a very good book which I bought from kindle. In my job as a network engineer I have to read a lot of books about computing but they are mostly books connected to my job in some way. This book is about a method of project management which is specifically for software development teams. I was so ignorant of this subject I thought agile & scrum were programming languages. I've seen books advertised on kindle about agile & scrum though. I think if you were involved in computer programming you would love this book. I must admit the book was a bit complicated for me. One of the main principles of agile is that things like meetings should keep to strict time limits ie if you are working on a 1 week project you have a 1 hour meeting. These meetings are called scrums. The idea behind that is that your programmers are working on their code as much as possible. Believe it or not in some software houses they only spend 20% of their time doing that which is unacceptable. Another problem is that some companies get the programmers to do the testing which in agile you have people who have a specific job doing that. I have read before that given the huge amounts of code that need to be written it's virtually impossible to write a program that doesn't have bugs. The best you can hope for is that the program only has occasional problems. That's why companies often release patches & why they say you should always give the company a few months to iron out any problems when a new program comes out.