|
Countdown to Agility Jean Tabaka believes in the power of an entire agile organization. These ten characteristics of an agile organization may seem counter to market success, but she explores why they are wholly embedded in twenty-first century business success.
|
|
|
Scrumdamentalism It's been said that, over time, charismatic movements often evolve to become "bureaucratic"—focused on a set of standardized procedures that dictate the execution of the processes within the movement. Has Scrum evolved to this point or is there still a place for agility in our processes?
|
|
|
It Takes a Village Pair programming is an Agile practice that has been shown to greatly improve code quality without a huge increase in development time. This article explains the ins and outs of pair programming and some things you need to consider before you tell team members to grab a partner and get programming.
|
|
|
How Agile Practices Reduce the Top 5 Requirements Risks Requirements risks are among the most insidious risks threatening software projects. Whether it is having unclear requirements, lack of customer involvement in requirements development, or defective requirements, these troubles are a major culprit in projects that go awry. As requirements expert and agile coach Ellen Gottesdiener explains, agile practice can go a long way in mitigating the top five requirements risks.
|
|
|
Adapting Inspections to the Twenty-first Century How do you adapt inspections to a twenty-first century distributed workforce? A key part of the inspection process is the team meeting, which provides peer pressure to participate and consensus on defects. Teams working in multiple time zones have limited opportunities for the team meeting. A list of requirements and the functions needed to solve this problem based on real-world experiences should help anyone faced with this problem.
|
|
|
Putting the Kart before the Horse? Go-karting is where most of the current Formula One racing drivers first learned the basics of race-craft. Antony Marcano, a former kart racer himself, recounts a father-and-son racing experience that helps him explain what goes wrong for many organizations that adopt Scrum as their first attempt to "go agile."
|
|
|
Time to Let Go of Obsolete Jobs Town crier, elevator operator, gas lamp lighter, carbon paper distributor, telegraph operator—you probably haven't seen many help wanted ads for these occupations lately. Why? Because these occupations are gone—obsolete, unnecessary, outdated. We just don't need them anymore. When new paradigms are created, new jobs are often created with them. And sometimes, existing jobs are no longer relevant.
|
|
|
What to Expect When You're Automating Testing After learning the basics of testing frameworks, writing tests for your existing codebase can be a daunting challenge. Where should you start testing, and what kind of tests will be the most effective? Learn how to kick-start your testing and some solutions to problems teams frequently encounter.
|
|
|
Scrum: Using High-impact Teamwork to Tackle Software Development Projects For organizations trying to do more with less in the current economy, knowing where to turn for help can be a big question mark. But as Laszlo Szalvay of Danube explains, Scrum is one possible solution. This agile method of project management is quickly transforming the way software is developed by bringing teams together through frequent communication and high-impact collaboration, resulting in increased productivity and an ability to build a better product faster.
|
|
|
Do You Know Why You Are Doing That? It's easy to get caught up in the inertia of a project and forget to ask exactly what we are developing, who our customers are, and what their goals with our software might be. Few software projects have the time and budget to figure out what their project is through trial and error. Getting clarity on project focus not only helps productivity, working to create software that people actually need increases our chances for success.
|
|