|
2020 Best CIO Acceptance Speech (penned in 2010) In the 2010 article, ThoughtWorks consultant Tiffany Lentz pens the speech a successful CIO might write ten years hence in 2010. She talks about the ways that agile principles had become the norm in development and spread beyond software teams in into IT and corporate planning and project execution.
|
|
|
Insights From Three Agile/Lean Product Development Thought Leaders Here is what Mark Lines (Unified Process Mentors, Co-Founder) has to say:
The fact that basic agile concepts are so easy to learn, as well as the proliferation of certification courses with very little investment required has had both positive and negative effects. Certainly the mindshare of methods such as Scrum has exploded in our industry and people are excited about the benefits that agile can deliver in terms of elimination of waste and timely delivery of systems with immediate ROI.
|
|
|
The Marriage of Lean, Scrum and Extreme Programming (XP) Many flavors of Agile have emerged: Scrum, Lean, Feature Driven Development (FDD), and Extreme Programming just to name a few. These methods have numerous complementary and distinguishing features, but the gamut of choices can be confusing and disorienting - as if being told to choose the best from 31 flavors of ice cream. Return on Investment (ROI) is important to me, so Lean must be the answer. But wait, I also want to be agile with my business priorities so I’ll choose Scrum. We are left wanting a simple question answered: “Which Agile method should I choose for my organization?”
|
|
|
Using Product Portfolio Management to Improve the Efficiency of Teams Product portfolio management has become an essential discipline for all development organizations that want to achieve enterprise agility. The repeated process of selecting, sizing, and prioritizing the work to be done ensures that their development teams are delivering the most valuable products and enhancements for the business’ clients. This is required for both external clients in the case of product companies and for internal clients in the case of IT organizations. However, the subject of this paper is another, possibly even more important, reason: avoiding the overloading of the organization’s development teams which greatly lowers their efficiency.
|
|
|
Project Portfolio Decisions—Decisions For Now If you are anything like me, you have a to-do list a mile long. Because I work for myself, I have an integrated list of everything I need to do: projects for clients, books to write, articles to write, columns to write, presents to buy, house maintenance, clothes to organize, office cleanup. The list is long and never-ending.
|
|
|
Rocks into Gold: Part 4 This short book by Clarke Ching is a "biztech" parable for software developers who want to survive—and then thrive—through the credit crunch. We have republished the book in a four-part-series. In part four, our characters pitch Bob's plan to MegaCorp. But will business politics get in the way of a good idea? Follow the story as our characters fight to keep their jobs by implementing creative business ideas and management skills taken from agile development.
|
|
|
What’s a Tester without a QA Team? When a tester joins an agile team, she leaves her Test or QA team behind. Often, her old QA team is disbanded altogether. Without the support of a QA team, she might feel abandoned, especially if she now reports to a development manager. She’s in danger of becoming isolated, having lost the phased and gated process that guided her old team. She may feel pushed to the sidelines and like she’s lost any control over quality.
|
|
|
Agile Developer’s Journal: A Day in the Life People are creatures of habit, particularly programmers: We seek consistency, whether it is the tried-and-true waterfall/SDLC method or our morning routine of reading the newspaper with a hot cup of coffee. Companies or projects looking to adopt an agile process neglect the fundamental concern of an individual developer: "What will my day to day look like working in an agile environment?"
|
|
|
An Introductory Acceptance Test "If you don't know where you are going, you will wind up somewhere else." Yogi Berra
This article is an excerpt from Ken Pugh’s upcoming book – “Lean-Agile Acceptance Test Driven Development” to be published by Addison-Wesley. Debbie, the developer, and Tom, the tester, are introducing acceptance test-driven development to Cathy, the customer.
The Triad – Tom, Debbie, and Cathy – are in their second meeting together. Debbie describes an example of an acceptance test and four ways that an acceptance test can be executed.
|
|
|
The "One Right Way" For those who believe there has to be one right way to do something, especially in software development - there can be. But that one way isn't likely to come from a single individual. Through collaboration and teamwork, some of the greatest single ideas have evolved.
|
|