If we don’t identify the champion of the endeavor to convert to agile processes, we can’t keep them informed of progress. Their expectations need to continually adapt to progress just like every element of agile.
Agile
Posted on:
Going Agile, 10 Mistakes: Ignore the Corporate Culture
Many companies operate with each department acting as a silo. Agile techniques rely upon cross-functional contributions. When there are barriers (“not my jobâ€, “not your jobâ€) within an organization, they have to be addressed before agile will work.
Agile
Posted on:
Going Agile, 10 Mistakes: Go Fast To Go Fast
In this mistake, Levent warns us that “just doing it†without training and explaining won’t work. Everyone needs to understand exactly what agile is and what it isn’t.
Agile
Posted on:
Going Agile, 10 Mistakes: Go All In
Levent points out that the biggest mistake is to not do a pilot project, but rather to convert a large and risky project – or even worse, all projects. He points out that it is a mistake because you won’t have time to learn from mistakes.
Agile / Software development
Posted on:
Seven Core Elements of Agile
Mishkin Berteig at Agile Advice writes an excellent essay on the seven core practices of being agile. Understanding these elements is the first step in getting past the hype and fud of the agility dilemna. Promoters of particular agile practices, as well as detractors use hyperbole and extreme examples to make their points. While very effective techniques for arguing, inspiring and motivating, hype and fud detract from learning, teaching and understanding.
Agile / Process Improvement / Software development
Posted on:
Making Agile Offshore Teams Work
Agile processes stress communication and colocation. Splitting a team into on and offshore resources inhibits the first and prevents the second. Teams struggle to resolve this apparent conflict of interest. Applying best practices (for any team) to address these challenges makes it possible. Martin Fowler provides us with great guidance based on years of experience with his company.
Agile / Foundation series / Process Improvement / Software development / Test Automation / Testing
Posted on:
Foundation Series: Continuous Integration
Continuous Integration is the software development and quality process where all team members merge their code and verifies it frequently – at least daily. This verification project includes both an automated build process and automated testing. The main benefits of continuous integration come from risk-reduction and cost-reduction.
Agile / Product Management / Project Management / Software development
Posted on:
Agile’s Biggest Strength is Agile’s Biggest Weakness
Agile works because it is designed to help teams adapt to changes in direction. Agile is designed to minimize the pain of changing requirements. Agile proponents believe the premise that requirements will change and no amount of upfront planning will impact that. They believe that the requirements simply do not exist until after something has been built. Agile processes save a lot of time by not doing big upfront requirements gathering or design work. They also don’t involve big up-front planning. They do small planning work. And they do it again and again, throughout the project. This works because they minimize wasted planning effort.
Agile / Process Improvement / Software development
Posted on:
Getting agile – should we?
Should we adopt an agile process for our team? Methods and Tools has posted a two part article titled Adopting an Agile Method. In thier article, they explore five areas of consideration. We provide our thoughts on each area. Five areas to consider (from the article) Our organization’s culture Our […]