Browsing All posts tagged under »Agile software development«

Meaningful Work – Busy Work

September 27, 2012 by

0

Meaningful Work versus Busy Work was the central theme of a presentation and discussion I shared with the PMI Heartland Professional Development Day on September 17, 2012.   The title was “Undercover Agile”.  The premise was sorting through what’s meaningful and busy work in daily project management practice.  Once sorted, high performance organizations and project managers focus […]

Function over Form – Don’t go Delores on me!

March 12, 2012 by

0

Over the last several months I had the opportunity to work alongside some wonderful people doing some great things.  From time to time a quirk surfaced.  I love quirks because they’re opportunities to grow. One quirk I saw I’ll call “Delores Umbridge” – in honor of the character from Harry Potter.  Delores was a most […]

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 9 – Agility is a result of technical excellence and good design

February 12, 2011 by

1

The ninth principle of agile brings in important aspects of enterprise architecture and system design. Technical excellence is a board term.  it can be applied to hardware, software, network infrastructure, process management, project management, programming, release management, etc.  I also think of enterprise architecture I hear technical excellence.  While Agile is change driven, that does […]