Browsing All posts tagged under »Scrum«

Stand up meetings – not just for software or Agile anymore

February 20, 2012 by

0

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 […]

Agile Principle 12 – Team reflects, tunes and adjusts

February 15, 2011 by

1

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 […]

Agile Principle 11 – Self Organizing teams produce best architectures, requirements and design

February 14, 2011 by

1

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 […]

Agile Principle 10 – Maximize work NOT done!

February 13, 2011 by

6

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 […]

Agile Principle 7 – Working Software

February 10, 2011 by

4

  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. […]

Agile Principle 2 – Changing Requirements

February 5, 2011 by

5

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.   […]

Agile Principle 1 – Customer Focus

February 4, 2011 by

4

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 […]