The Latest
 |
What If Quality Shouldn’t Be Job One?[magazine] We live in a consumer-oriented society, where we are taught to expect that everything that we buy or create must be the best. Clearly, quality is considered to be a top-selling feature in many of the products that we buy. But what if it shouldn’t be? |
|
|
Kudos from GetAbstract for Manage Your Project Portfolio[article] The nice folks at getabstract like Manage Your Project Portfolio: Increase Your Capacity and Finish More Projects. Some of the takeaways they highlight are: |
||
|
Configuration Management and DevOps with Jez Humble and Bob Aiello[article] In this excerpt from an interview recorded at this year's Better Software and Agile Development Practices East conferences, authors Bob Aiello and Jez Humble discuss the challenges and the rewards of instituting configuration management and DevOps practices. |
||
|
Reflections on a Moment of Conflict[article] Everyone can recall a moment in their life where there was conflict with a coworker, or team member. How did you handle that situation? How did the other party involved handle it? By taking a minute to look at how either of you could've acted instead, you may be able to prevent a future incident. |
||
 |
Specification by Example: Collaborating on a Scope without High-Level Control[article] Understanding what the business users are trying to achieve can significantly help you focus the project on things that really matter. In this excerpt from Gojko Adzic's book Specification by Example, the author offers some tips for effectively collaborating on the project scope when you don’t have high-level control of the project. |
|
|
Leadership, Management, Transitioning to Agile[article] Johanna Rothman has worked with several management teams who want her to train them or their project managers to take over the agile training. While on the surface this doesn't seem an unreasonable request, when one considers the self-managing, self-organizing nature of an agile team, the incongruity of this thinking begins to shine through. |
||
 |
How to Give an Accurate Answer[article] Scott Ames explains the Test Requirements Agile Metric and offers a real-world example of its use in software estimation. |
|
|
Why Focus on Continuous Integration for Programs?[article] I hope that this 3-part series on how to move to continuous integration and how to evaluate if it’s worth moving to continuous integration on your program convinced you moving to continuous integration was worth it for programs. |
||
 |
Story Mapping the Wrong Way[article] When Lisa Crispin’s team got an opportunity to put the story mapping ideas she picked up from Jeff Patton into practice, they excitedly rushed into it and missed a few steps. Find out what happened, what didn't happen, and what they learned from it all. |
|
| Is the Cost of Continuous Integration Worth the Value on Your Program?, Part 3[article] | ||
|
Is the Cost of Continuous Integration Worth the Value on Your Program?, Part 2[article] Let’s set the context (which I did not do in my most recent post–sorry). |
||
|
The Pursuit of True Agility[article] Adrian Cho looks at agile practices, invention, and change through the allegory of musical experiences. |
||
|
Agile Requirements Management with Keith Johnson[article] Keith Johnson is vice president of product development at Jama Software. in this Sticky ToolLook interview, he discusses some of the changes that agile development has brought to the requirements management process. |
||
|
Is the Cost of Continuous Integration Worth the Value on Your Program?, Part 1[article] I like continuous integration. A lot. I started being an aficionado of continuous integration back in my senior year of university . It was my very first (and last) team project in my college career. There were three of us. The project manager waited until the night before the project was due to get us all together (argh #1). I had completed much of my code several weeks before (argh #2: who can remember what they’d written several weeks ago?). We wrote code madly for hours, and then tried to make it work, starting about 9pm. It didn’t work. We stayed up all night (argh #3). |
||
 |
Two Measures of Development Effectiveness: Predictability and Optimization[article] Nearly every CIO or VP of R&D is struggling to improve their time to market while increase the number of features delivered within stagnant or shrinking budgets. Two objectives of software development teams will address this need are to improve predictability and optimize productivity By combining views of predictability and productivity of the development activity, the team and its stakeholders can quickly and easily tell if the development is on track, if predictability is improving, and if team members are self-aware enough to improve their overall output. |
Pages
Agile Connection is one of the growing communities of the TechWell network.
 Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery. Join the conversation now! |