Browsing All Posts filed under »Agile«

Marketing has a New Lean Diet

October 5, 2012 by

0

In today’s economic climate, it’s not uncommon for organizations to drastically cut their marketing budgets in an effort to improve their bottom line. And yet, during this fiscal downturn, the need is even more prevalent to reach consumers, improve branding and broaden market shares. Marketing staff must find ways to identify opportunities in both new […]

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

YAGNI – You Ain’t Going to Need It – anyway.

November 6, 2011 by

0

  In the midst of some infrastructure / application remediation work for a great client in Omaha (insurance company) the concept of YAGNI came to mind.   There’s a couple of quick reads for you. First a sort of “anti hero” opinion piece from one of the early members of Borland (Mike Rozlog) who apparently still holds […]

Pragnalysis team announce launch of free Requirements Management Software Tool – “ReqLine”

May 16, 2011 by

0

On medium and large scale projects, requirements management can become a difficult overhead.  Teams that rely on spreadsheet and word-processing software to create and manage requirements documents often find it difficult to maintain the traceability and inter-dependencies between requirements.   We all know the value of tracing, tracking and maintaining our requirements documents, but until now […]

Business Analysis Technique #3 – Brainstorming

March 1, 2011 by

2

The whiteboard.  The dry eraser.  The multi-color pens.  The overbearing meeting participant.  Those four things often come together when thinking of brainstorming.  It’s a technique among multiple management nexus disciplines and at the heart of agile, business analysis and project management. It can produce great results from a team. The Business Analysis Body of Knowledge […]

Lean Startup (for product and software development)

February 21, 2011 by

1

The tenth anniversary of Agile is upon us.  We just concluded a 12 part review of the Agile Manifesto. Agile was a software development out to business, innovation.  Or it could have been called “geeks to execs”.  Now for a fast forward, to today. Emerging trends and practices include those that fuse business, design and […]

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

Agile Principle 8 – Constant Pace of Development

February 11, 2011 by

4

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

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 6 – Face to Face Interaction

February 9, 2011 by

5

  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 5 – Motivate, Support and Trust People

February 8, 2011 by

5

Is it a radical concept, motivate, support and trust people?  No.  Not really. The Agile principle of building projects around motivated individuals is clearly a Theory Z , Y or Herzberg management approach — people want to achieve and when they do, advance that performance to even higher levels.  It doesn’t fit well with the […]

Agile Principle 3 – Deliver Work Frequently

February 6, 2011 by

6

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

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