background preloader

AGILE

Facebook Twitter

VUCA - KATA - Hoshin Kanri. The Eight Pillars of Innovation.

TSU

Design Thinking Network. BUSINESS CHANGE AND INNOVATION. Why the Lean Start-Up Changes Everything. Photography: Courtesy of the artist and the Wallace Trust Artwork: Sara Hughes, Download, 2005, acrylic on linen, 1.5 m x 1.5 m, Wallace Trust Collection Launching a new enterprise—whether it’s a tech start-up, a small business, or an initiative within a large corporation—has always been a hit-or-miss proposition.

Why the Lean Start-Up Changes Everything

According to the decades-old formula, you write a business plan, pitch it to investors, assemble a team, introduce a product, and start selling as hard as you can. And somewhere in this sequence of events, you’ll probably suffer a fatal setback. The odds are not with you: As new research by Harvard Business School’s Shikhar Ghosh shows, 75% of all start-ups fail. But recently an important countervailing force has emerged, one that can make the process of starting a company less risky. The lean start-up movement hasn’t gone totally mainstream, however, and we have yet to feel its full impact. The Fallacy of the Perfect Business Plan 1. 2. 3. Stealth Mode’s Declining Popularity 1. Systems Thinking. Logged off - Westpac NZ Online Banking.

The Current Direction of Agile. In the last couple of years, Agile adoption has increased quite a bit, letting a number of people experience and challenge different elements of the Agile processes.

The Current Direction of Agile

This increased exposure and usage has made some try out different solutions to different challenges than what was originally proposed by the people that came up with the Agile processes. This is a core part of Agile, to change the process over time and make it more effective. This article will focus on some of the recent trends within the Agile community by briefly describing some alternatives to today’s well known Agile processes. Particularly focusing on estimation, forecasting deliverables and the increased impact Lean manufacturing has had on the Agile community. Lean I will not cover Lean specifically, but I will briefly cover some of the Lean principles, practices and tools which are relevant to the other processes and tools covered in this article.

Waste Just-in-time (JIT) Work In Process (WIP) Pull based systems Waste. Process & Practices. Research on Process & Practices Defect Identification & Management Practices in Software Development – Part 2 This research item is the second of two that look at the defect identification and management practices in software development.

Process & Practices

Almost all software development approaches incorporate processes for tracking, recording, measuring and resolving defects. Defect Identification & Management Practices in Software Development - Part1 This research item is one of two that look at the defect identification and management practices in software development. What Influences the Mood of Agile Teams? Team mood plays a key role in agile software development, as people are working closely together every day to iteratively deliver a product to their customers and satisfy the needs of their stakeholders. Common Causes of Team Conflict Team collaboration is one of the primary focuses of Agile. Major Software Development Trends for 2013 Top Application Lifecycle Management (ALM) Toolsets. Story-Splitting-Cheat-Sheet.pdf.

Agile Stories

Kaeru. User stories reimagined Since the concept of user stories was introduced it has been used (and misused) in so many ways.

kaeru

The stories were intended to replace formal requirements (that were, for practical reasons, not followed anyway) and use cases (that were way too cumbersome to write). A story is supposed to be a promise to have a conversation around the subject of the story, to eliminate misunderstandings through speech, not writing. This means that a user story can be very high-level and somewhat abstract, and the discussion around it will make it more tangible.

Mike Cohn wished to formalize the user story a few years back. As a [role] I want [feature] so that [benefit] To explain something with the focus on who wants it helps the person reading the story to put herself in the shoes of this person. But, since it requires a little bit more thinking (and hopefully research) to find out who is wanting this feature and why, the story has been shortened to: Patterns for Splitting User Stories - Agile For All. Good user stories follow Bill Wake’s INVEST model.

Patterns for Splitting User Stories - Agile For All

They’re Independent, Negotiable, Valuable, Estimable, Small, and Testable. The small requirement drives us to split large stories. But the stories after splitting still have to follow the model. Many new agile teams attempt to split stories by architectural layer: one story for the UI, another for the database, etc. This may satisfy small, but it fails at independent and valuable. Over my years with agile, I’ve discovered nine patterns for splitting user stories into good, smaller stories.

(Note: As with any pattern language, I didn’t invent these patterns, I’ve just observed and compiled them. How Small? Www.agileforall.com/wp-content/uploads/2012/01/Story-Splitting-Flowchart.pdf. Essential skills for agile development. Manning Becoming Agile May 2009.