Ask the Experts: What is Great Design?

This week, in conjunction with a workshop OpenView hosted on user experience process and product design, we’ve gathered a panel of industry experts who each know a thing or two about designing successful products.

the outcome

Posted in Agile, Design Thinking, Scrum | Leave a comment

Our Development Process: 50 Months of Evolution

null

click here for full article

Posted in Agile | Leave a comment

Scrum: Inside the Sprint Retrospective

Posted in Agile, Scrum | Leave a comment

Lean Manufacturing Example Toyota Plant Kentucky

Posted in Lean | Leave a comment

Sir Jonathan Ive: The iMan cometh

Mark Prigg meets Sir Jonathan Ive, the British man behind the design of Apple’s iconic products

more …

Posted in Design Thinking, Thinking tools | Leave a comment

Technical Debt Is Now Costing Us $3.61 Per Line Of Code

A series of blog posts by Jonathan Bloom from CAST software summarized the company’s report on technical debt. Among the key findings:

CAST now estimates technical debt to cost companies $3.61 per line of code.

35% of those items considered to be technical debt were severe enough to adversely affect support of the system studied, potentially resulting in security, performance or uptime issues.

Outsourced and in-house developed applications didn’t show any difference in structure quality. The same was true for onshore and offshore applications.

Java EE applications were the most prevalent among those studied and received significantly lower performance scores as well as carrying greater technical debt than other languages.

Established development methods such as agile and waterfall scored significantly better in structural quality than custom methods, while waterfall scored the highest in transferability and changeability.

COBOL applications scored the highest in security, while .NET applications received the lowest security scores.

Modularity of systems may contribute to lower quality and reduced performance.

Government systems tend to be the lowest in maintainability.

The more frequently the code is released the higher the technical debt.

This is the second year that CAST has produced the report. This year’s data was compiled from 160 different companies from a hodgepodge of industries. The total number of systems studied was 745, representing a combined 365 million lines of code.

Analysts at Gartner have also exposed and cited the growing problem of technical debt in organizations. David Norton wrote a blog post likening the problem to a time bomb that can be ignored for a period of time, but at some point it will cause serious harm to the affected organization.

CAST and other thought leaders on technical debt suggest that organizations should be accounting for technical debt as part of their capital budgets. Israel Gat’s approach for monetizing technical debt was covered by InfoQ in 2010.

full article on infoq

Posted in Agile, Lean, Technical excellence, Thinking tools | Leave a comment

The Business Model Canvas

Your business model – on one page

The Business Model Canvas, is a strategic management and entrepreneurial tool. It allows you to describe, design, challenge, invent, and pivot your business model.

The Business Model Canvas

Posted in Creativity, Thinking tools | Leave a comment

Core Practices for Continuous Delivery

Continuous delivery allows teams to reduce dramatically the transaction cost of releasing high-quality software, so you can do it much more frequently, providing a much richer and faster feedback cycle from users back to product teams. But, in turn, you need to change the way you think about managing the flow of work through the software delivery process.

This article presents five practices of continuous delivery that can help you to create the most efficient path from hypothesis to continuous feedback. Following the practices outlined here, you can deliver single-feature or small-story batches that dramatically decrease the time needed to build a new product or new release, testing and moving forward on successful features and redesigning or dropping features that fail (or that users show they don’t really want). The five practices discussed in this article are:
* Start with a minimum viable product (MVP).
* Measure the value of your features.
* Perform just enough analysis up front.
* Do less.
* Include feature toggles in your stories.

form www.scrumexpert.com

Posted in Agile, Scrum | Leave a comment

What I Learned from Taiichi Ohno

Today is Taiichi Ohno’s birthday. Were he alive, the primary developer of the Toyota Production System would be turning 100 years old.

here is the insightful, colorful story of Ohno providing direct, intensive coaching for an executive of Daihatsu.

with compliments to John Shook LEI

Posted in Lean, Thinking tools | Leave a comment

Software Engineering for Software as a Service

Again free / online education movement more

Posted in Creativity, Technical excellence, Thinking tools | Leave a comment