At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. As this is the 12th principle, lets kick off by reminding ourselves about the Agile manifesto that is behind all of the principles. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer…
The 11th post in my series on the Agile principles is ….. Self-organizing teams. “The best architectures, requirements and designs “emerge” from self-organizing teams.” How can that be???? Surely a team needs a leader dictating the direction to deliver the best results. Just as a sports team needs a coach / manager. Or does it????…
The Agile manifesto is …. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan When I first read this it felt a little hippy to me, I imagined a 1970s office full of scruffy looking programmers wearing flares and stroking their…
What is the best way to project manage a CRM implementation??? Agile with a capital A, seems to have started around 2001. But I know many programmers and project manager who were following a rapid Agile like approach to devlopment many years before the term was coined. Whilst Agile is a popular approach to management…
The seventh principle in the Agile manifesto is “Face-to-face conversation is the best form of communication”, this is something I truly believe in. “BUT”, I hear you say, face to face communication isn’t always achievable. The people you want to speak to maybe be in another office or possibly off shore. Video conferencing goes a…
The fourth Agile principle is “Working software is the principal measure of progress”. Shouldn’t that be obvious! Well you’d have thought so. But the KPIs we use to measure progress on a project so often miss the point. How often do we count number of lines of code, man hours allocated to the build, number…
“Sustainable development, able to maintain a constant pace”, the fifth principle of Agile. Sustainability makes this sound a bit hippy right? Wrong! Sustainability here relates to conducting development in a professional, consistent and therefore measurable / repeatable way. Any development team has a velocity at which they can cut code, the trick is to understand this…
The sixth Agile principle is “Close, daily cooperation between business people and developers”. The principle here is to get the business people and the developers working closely together, hopefully the result will be that the business representatives really help to shape the final solution whilst the developers also gain a deeper understanding of the business…
The second Agile principle is “welcome changing requirements, even late in development”. Sounds simple enough and as a principle it is. Except for the fact that very often this doesn’t happen. Welcoming change is not about creating a robust formal change process. I’ve worked for one organisation who insisted they embraced change they had a formal…
“Our life is frittered away by detail. Simplify, simplify, simplify! I say, let your affairs be as two or three, and not a hundred or a thousand; instead of a million count half a dozen, and keep your accounts on your thumb-nail.” This quote from Henry David Thoreau kind of sums up this part of…
Microsoft Dynamics 365 