Stand up. Sit down. Which is better for the team, productivity, your company? The trend is stand up for a short burst of action and accountability among all types of business teams. A hall-mark of rapid software development (1990′s) and Agile (manifesto in 2001 onward) the stand up meeting has progressed rapidly beyond software, to… [Read more…]
February 15, 2011 by David Kohrell
The last principle of the Agile Manifesto provides for learning and adjustment by the team. This adjustment allows for continuous process improvement. Teams don’t allow themselves to become stagnant or stale – they change and become better. The manifesto doesn’t proscribe how often and allows some leeway. The definition of “at regular intervals” provides sufficient… [Read more…]
February 14, 2011 by David Kohrell
Agile manifesto – principles number 1 – 10 were ones I could embrace or at least accept. And yes I know it’s your 10th birthday this month. But really, number 11 is a difficult one for this control oriented, project management/ manager type to swallow. You’re saying that self-organizing teams can get it done? Yeah… [Read more…]
February 13, 2011 by David Kohrell
The tenth principle of the Agile manifesto may be my favorite one – simplicity, the art of maximizing the amount of work NOT done. Too often methodologies, frameworks and process improvements get mired down in heavy process and documentation. It’s a balancing act. It’s important to be neither too much, nor too little – just… [Read more…]
February 10, 2011 by David Kohrell
The seventh principle of the Agile Manifesto is the simplest and shortest one. Working software is the primary measure of progress. That simplicity belies a profound philosophy and modus operandi That is the outcome trumps the process. This philosophy grates and goes against the grain of conventional wisdom. Have a problem, add process.… [Read more…]
February 5, 2011 by David Kohrell
Re·quire·ment n. 1. Something that is required; a necessity. 2. Something obligatory; a prerequisite.¹ Among the twelve principles of Agile, that one that evokes a good amount of debate is changing requirements, even late in development. This contrasts from plan driven approaches to development that “freeze requirements” and lock those in through development and deployment. … [Read more…]
February 4, 2011 by David Kohrell
The four values of the Agile Manifesto (Individuals, Customer, Working Software and Change) are further elaborated in twelve principles. The first principle is “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. “ The first line provides the goal – satisfy the customer. That customer focus brings Agile… [Read more…]
February 3, 2011 by David Kohrell
One of my favorite movie lines is from the Princess Bride. In it the hero is told he must go back to the beginning. When the movie reaches one if its many climaxes – Indigo (hero) exclaims “I am waiting for you, Vizzini. You told me to go back to the beginning. So I have.… [Read more…]
February 1, 2011 by David Kohrell
We make stuff happen! Adjust some capital letters and you get WEMSHA (pronounced Whim Shaw)! That’s been a working term for us at TAPUniversity the last several years. A WEMSHA mindset helps keep focus among competing methodologies, approaches and flavors of the month – Agile/SCRUM, FDD, Lean, SDLC, RUP, Iterative, Incremental, Change or Plan… [Read more…]
January 28, 2011 by David Kohrell
The essential concept of progressive elaboration is that organizations, teams, and people do not have to have all the pieces and parts fully known before beginning. Don’t get me wrong, having details is important, but not for everyone. This approach fits very well with the change driven methodologies of Agile and Lean Software Development. Communication… [Read more…]
 | Ade on Conflict of Interest–The… |
| Wideband Delphi « TA… on Wideband Delphi | |
 | fahadusmani on To-Complete Performance I… |
 | John on If Santa Thinks Chimneys Quali… |
 | DD on Organizational Process As… |
 | Olu Olufowobi on Make-or-Buy Analysis |
 | Arun on Organizational Process As… |
February 20, 2012 by David Kohrell
0