Subscribe:
RSS feed
Instantly usable and helpful information for project management, agile/SCRUM, business analysis, IT strategy and compliance and lean – six sigma.
Browsing All posts tagged under »Agile software development«
Meaningful Work – Busy Work
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 Dave Kohrell
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 Dave Kohrell
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 Dave 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 […]
Agile Principle 11 – Self Organizing teams produce best architectures, requirements and design
February 14, 2011 by Dave 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 […]
Agile Principle 10 – Maximize work NOT done!
February 13, 2011 by Dave 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 […]
Agile Principle 9 – Agility is a result of technical excellence and good design
February 12, 2011 by Dave Kohrell
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 […]
Agile Principle 8 – Constant Pace of Development
February 11, 2011 by Dave Kohrell
Sprint or marathon? 100 meters, 5k or 26.2? Slow endurance or high intensity interval workout (HIIT)? Anaerobic or aerobic? Rare combination of talent like Michael Johnson (pictured) who excelled at the 200 and 400 meters? If Agile were a workout it would seem to fit in the sprint, 100 meter, high intensity, anaerobic side of […]
Agile Principle 7 – Working Software
February 10, 2011 by Dave 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. […]
Agile Principle 6 – Face to Face Interaction
February 9, 2011 by Dave Kohrell
Face to face interaction provides for the most effective form of communication. The sixth Agile Manifesto principle advocates face-to-face conversation. A sticking point for adopting Agile is the dominance of virtual teams within an organization and among different organizations (in a vendor – customer relationship or within a supply chain for example). Bringing virtual […]
Agile Principle 4 developers and business working directly together
February 7, 2011 by Dave Kohrell
Unleashing your developer geeks on unsuspecting business people was quite risky in the 1990’s. Why those geeks may be a bit rough, un-kept and may spill the beans (truth). They clearly have not transformed in “McDreamy” yet (Patrick Dempsey). They’re still commuting to work on their lawn mower. Seems a little silly now. The prevailing […]
Agile Principle 3 – Deliver Work Frequently
February 6, 2011 by Dave Kohrell
Steve McConnell (Borland, Independent, then Microsoft) and Philippe Kahn (Borland founder) are two notable software engineers from the late 1980’s to present day. They introduced the concept of a daily build and smoke test in the late 80’s while at Borland. Its ability to roll out cutting edge development tools (Turbo Pascal first, Paradox second) […]
Agile Principle 2 – Changing Requirements
February 5, 2011 by Dave 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. […]
Self Paced – Online ACP, CBAP, LSS or PMP – $99.00
Feedback!
Live Feed
TAPUniversity 
September 27, 2012 by Dave Kohrell
0