The Latest
 |
A Galaxy of Patterns[magazine] The Gang of Four's design patterns have a special place in many programmers' hearts. But it's time to look beyond the GoF twenty-three and realize they aren't the only patterns in the universe. |
Neil Harrison
June 24, 2008 |
|
How to Fail with Agile[magazine] A switch to agile often conflicts with personal career goals such as maintaining the status quo and working no harder than necessary. These twenty guidelines will help you sabotage your agile project, helping you fail quickly and spectacularly. |
||
|
A Framework for Agile[article] Bob Aiello discusses how CM and agile practices can go hand in hand - provided that you have a solid framework to work with. With agile's popularity seemingly always on the rise, alongside the need for CM, learn how having both benefits everyone onboard. |
||
|
How to Fail Less and Enjoy More[magazine] The shiniest software application in the world, shipped on time and under budget, is a failure if it doesn't make someone's job easier. Failures cost us customers and money. How can we design software that our customers want to use and that will reduce our cost of failure? |
Frédéric Boulanger
May 30, 2008 |
|
 |
Advice for the New Leader[magazine] As a new manager it's easy to fall into the trap of taking on more of your team's responsibilities than you should. Learn how to guide your team to success by stepping back and letting team members solve their own problems, learn from their mistakes, and most of all do what you hired them to do. |
|
|
The Mission Is the Message[magazine] A mission statement is supposed to guide and inspire the members of an organization as well as define the organization's purpose, the business it is in, and its responsibilities to its clients. Is your statement sending the right message? |
||
 |
Stop The Insanity! Using Root Cause Analysis to Avoid Repeating Your Mistakes[magazine] We've all heard Einstein's definition of insanity, and it definitely holds true in software development. We "are" going to make mistakes in product development, but root-cause analysis can help us understand those mistakes and be proactive in not repeating them. |
|
 |
The Myth of Risk Management[magazine] Risk management is an illusion. We must recognize that software projects are inherently risky and admit to ourselves that it's not the known problems that are going to cause our projects to fail. It's the risks that are unmentionable, uncontrollable, unquantifiable, or unknown that make projects crash and burn. |
|
 |
Agile Model-Driven Development[magazine] Despite what you might have heard, modeling is an important part of agile software development. Find out how agile model-driven development fits into the overall agile development lifecycle in a lean and streamlined manner and can improve productivity on your team. |
|
 |
A ''D'' in Programming, Part 2[magazine] In his final pitch for the D programming language, Chuck brings to "closure" (pun intended) a running example from previous Code Craft articles while exploring some powerful features of the D language. |
|
|
Know Where Your Wheels Are[magazine] Drawing from his experiences while learning to drive, Michael applies lessons he learned from written rules, experiential learning, and the advice of mentors to teaching new testers some valuable skills. |
||
|
The Practice of Good Release Management Processes in CM[article] We build software as part of a system or as its own entire product. The goal is to meet the requirements established by the customer, the market and/or the cost/benefits analysis. Product releases are meant to move us from some starting point to our ultimate product over a period of time: months, years or even decades. Release management starts not with the delivery of software, but with the identification of what we're planning to put into the product. The timing and content of releases helps us to manage releases so that they are not too onerous on the customer and so that we stay in a competitive position with our products. Good release management processes will ensure that you know what is going to go into your product, what actually went into the product, and what changes the customer is going to realize upon upgrading. |
||
|
Release Engineering Best Practices[article] G |
Anonymous
May 26, 2008 |
|
 |
SCM Essentials for Small Teams[article] Very small teams think that SCM (software configuration management) is not for them. Even the name sounds like a big thing: CM, configuration management. "Why should I care?" They |
Pablo Santos
May 26, 2008 |
|
An Agile Approach to Release Management[article] For teams practicing Agile Software development, value working software over other artifacts, a feature from the release plan is not complete until you can demonstrate it to your customer, ideally in a shippable state. Agile teams strive to have a working system ("potentially shippable") ready at the end of each iteration. Release Management should be easy for an ideal agile team, as agile teams, in theory, are ready to release at regular intervals, and the release management aspect is the customer saying, "Ship it!." |
Pages
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.