Browsing All Posts filed under »Software Development«

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 #26 – Scenarios and Use Cases

March 2, 2011 by

6

Several years ago I shared a series of articles in the Rational Edge for IBM that showcased real life applications of use cases and incremental development.  Two of those articles focused on replacing a legacy unemployment insurance system. The entire article provides a much more thorough introduction from that example – so take a quick […]

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