The Latest
|
Not Wanted on the Voyage[article] Back in the day of cross-Atlantic boat travel, luggage that wasn't needed during the long journey was labeled "Not Wanted on the Voyage" and stowed away below decks. In this column, Fiona Charles suggests that testers can also be viewed as heavy baggage and not exactly welcome by some parties during the journey of software development. To understand why others might think this way, Fiona takes a good, hard look at what testers do that could possibly make them undesirable team mates. |
||
|
Agile Product Managers and Product Owners: A Scalable, Nuanced Approach[article] In the first article of this three-part series, Dean Leffingwell describes a nuanced approach to the role of the agile Product Owner in the enterprise setting, concluding that the enterprise is likely to need both agile Product Owners and agile Product Managers to achieve success. |
||
|
Organizational Challenges[article] The following article is an excerpt from "Agile Testing" by Lisa Crispin and Janet Gregory. Part II Organizational Challenges When software development organizations implement agile development, the testing or QA team often takes the longest to make the transition. Independent QA teams have become entrenched in many organizations. When they start to adapt to a new agile organization, they encounter cultural differences that are difficult for them to accept. In Part II, we talk about introducing change and some of the barriers you might encounter when transitioning to agile. Training is a big part of what organizations making the transition need, and it's often forgotten. It's also hard to see how existing processes such as audits and process improvement frameworks will work in the agile environment. Going from an independent QA team to an integrated agile team is a huge change. |
||
|
An Agile Approach to Scheduling[article] When we schedule too many variables, things start to slip and soon the schedule is out the window. Paying attention to your project's constraints can help you set realistic scheduling goals that you will actually be able to stick to. |
Carlos Sirias
February 16, 2009 |
|
|
Raising the Bar with Test-Driven Development and Continuous Integration[article] A hallmark of truly agile teams is an unquenchable desire to continually find new and better ways of developing software. These teams believe that there really are no "best" practices, only practices which work better or worse for them. This line of thinking is even apparent in the first line of the agile manifesto stating "we are uncovering better ways of developing." In this article I will explore two of the most widely accepted agile development practices, test-driven development and continuous integration, and question how these practices can be made better with continuous testing. |
||
|
Group Coherence for Project Teams - Collaborative Interaction[article] The hyper-productive teams we have observed apply high rates of practical collaboration. We believe that fostering Collaborative Interaction leads to increases in productivity, yet performance is recognized at the individual rather than team level. In environments where collaboration is required, managers should avoid assigning project work and accountability to individuals. Inappropriate rewards for individuals are additional distractions from their collaborative project duties. |
||
|
Requirements Come Second[article] Despite our best efforts we need to know what we are going to code before we write the code. And as much as we might like to test before we write the code we can't really run tests until we have some code. Agile overlaps requirements discovery and implementation so coding can start with minimal or outline requirements but there is still a sequence. |
||
|
Tips and Advice - Manifesto for Agile Software Development[article]
Podcast
Bob interviews George Dinwiddie about the Manifesto for Agile Software Development. |
||
|
Agile 2008 - Adrian Mowat - Naked Agelist Podcast, Fitnesse, Big Batch Processing[article]
Podcast
Adrian Mowat and Bob Payne recorded this insightful podcast at Agile 2008, and discussed a wonderful variety of topics, including Scrum, technical practices, and Adrian's experience using Fitnesse. |
||
|
Introduction to Multi-Stage Continuous Integration[presentation] A full, continuous integration build and test is a key component of most agile processes. Unfortunately, as systems grow in size through consecutive iterations, these builds can easily take thirty minutes or more. |
Damon Poole, AccuRev
|
|
|
Agile Engineering for Architects[presentation] Agile development requires architects and architecture, but the current user story-centric approach ignores the qualities of systems, instead overly focusing on features and functions. |
Ryan Shriver, Dominion Digital
|
|
|
Picking the Right Test Automation Strategy for Your Project[presentation] The choice of a test automation strategy is a key determining factor in whether your test automation initiative will repay your investment, or become a sink hole devouring time and money. |
Gerard Meszaros, ClearStream Consulting
|
|
|
Retrospectives in Action - Looking Back at the Conference[presentation] In this last-day, last-hour session, Jean Tabaka invites you to apply a fundamental practice of agile teams-retrospection. |
Jean Tabaka, Rally Software Development
|
|
|
Scaling Agile Up and Out: A Tale from the Trenches[presentation] It seems like everyone wants to scale their agile teams. As projects grow in scope, the agile approach to software development needs to scale up to larger team sizes. |
Ade Miller, Microsoft Corporation
|
|
|
Agile Growing Pains[presentation] Often, examples of agile successes are presented in the context of small, software-only development teams. Michael Kirby describes what it took to deploy agile development techniques in a large, embedded software development organization. |
Michael Kirby, Xerox Corporation
|
Pages
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.