I have been giving this presentation as a introduction to project managment with a focus on introducing companies to the basic concepts of Agile. The presentation is aimed at PM Newbies and explaining agile to the managment teams more than the developers.
This is possible one of the most concise videos on SCRUM from Hamid Shojaee of Axosoft.
I just seen this video from “Global IT Consultancy” Thought Works it just made me laugh.
The key to building a good software development team is to focus on the development of the staff. In most software teams many learning opportunities are removed to focus on the commercial or time-line of the project. Practices such as the two weekly demo or paired programming are drop to free up more time. Agile is full of learning opportunities which will improve the individuals, team and then the software they produce. lets look at benefits to learning and the software created by Pair Programming in more detail.
Continue reading
The importance of the retrospective cannot be underestimated it in many cases is the worst performed element of the agile practices. I am currently researching different project managers and facilitators retrospective practices.
I am currently documenting my thoughts on this but I during my research I found this video from Google Tec Talks.
Clarke Ching from Agile Scotland invited the members of Agile Scotland to an event in Toshiba Medical Visualization Systems in Edinburgh, the speaker was Nancy Van Shooenderwoert. Nancy has been active in the Agile world for some time and is in many ways a evangelist.
The presentation was focused on software development in a safety critical environment, which is of interest to all of us as we all know the pain of software that has been developed with bugs in it.
![MPj04034140000[1]](http://www.ianburgess.me.uk/wp-content/uploads/2009/06/mpj040341400001-small1.jpg "Agile Retrospective Lessons Learned")
The one phase that is most often neglected in agile development is the retrospective, fulfilling the same role as lessons learned in other methodologies such as Prince2. Only paying lip service to the retrospective will have noticeable effect on the delivery of the project it is in this phase that misunderstandings are outlined and process that have not went well are addressed.
Some Project Managers focus on this in a very structured way moving from one defined stage to the next, I have over time come to believe that a structure is important to focus the meeting but a strict agenda has never really achieved the best results. What I want to outline are general principles that should be included in any retrospective, remembering that each section will naturally flow together and it is the PM job to bring them back to the necessary stage and maintain relevance and focus.
Lets look at what a retrospective should include:
RT @ianburgess Facebook as a Collaborative Knowledge Management System http://bit.ly/c748hE #UOKM
@DiscoverTheKey love the new brand, good to see its all working for you coffee soon? Working on "Makeup of Consultancy Industry" for Edinburgh Uni MBA consultancy panel tomorrow.
