Login
Username:

Password:


Lost Password?
Register now!

« 1 ... 28 29 30 (31) 32 »
Focus : A "Bones" Approach for Dead Projects
on 2007/9/26 8:40:00 (2162 reads)
Focus

Rest In Peace (from Latin requiescat in pace) is a sentence that typically appears on christian tombstones. Software development projects have usually the same destiny. Once they are finished, often the best thing that will happen is a little celebration for the project team. Nobody will formally look back at a project to understand what went well or wrong and why those things happen, so that this project can actually rest in peace and lessons learned could be used for the next projects.

Read More... | 3657 bytes more
Articles : Adopting an Agile Method
on 2007/9/19 22:50:00 (1743 reads)
Articles

The argument has been made: "We should be using an Agile software development method." And the command has rung out: "Make it so!" Now what do you do? How do you take that one-line "requirement", and make it so?

Adopting an Agile method is no different from any other change we might make to the methods and tools we use. We must determine why we are embarking on this course, choose the method that will satisfy the need most closely, then map out the path from where we are today to where we need to be. Then we can "make it so".

Read More... | 13865 bytes more
Articles : Refactoring
on 2007/9/17 23:34:47 (1692 reads)
Articles

Refactoring is a powerful technique for improving existing software. Having source code that is understandable helps ensure a system is maintainable and extensible. This paper describes the refactoring process in general and some of the benefits of using automated tools to reliably enhance code quality by safely performing refactoring tasks.

Read More... | 17696 bytes more
Articles : XP Testing Without XP: Taking Advantage of Agile Testing Practices
on 2007/9/13 3:21:09 (1534 reads)
Articles

In the rocket-fast late 90s, I struggled with using traditional software process and testing practices on e-commerce applications. Then I read Kent Beck’s Extreme Programming Explained and had an amazing ‘aha’ moment. Ron Jeffries sums it up best: Extreme Programming is a discipline of software development based on values of simplicity, communication, feedback, and courage. It works by bringing the whole team together in the presence of simple practices, with enough feedback to enable the team to see where they are and to tune the practices to their unique situation. (www.xprogramming.com)

Applying more discipline to traditional waterfall process had not helped my team. A new kind of discipline based on values such as communication, simplicity and feedback might be the answer! I immediately took an opportunity to join an XP team as a tester, and enjoyed working on XP teams for the next 18 months. Indeed, XP did allow us to produce high-quality e-commerce applications on time and on budget! Our customers were happy! We were happy! We struggled some with how I, as tester, could best contribute to the team, as the XP literature at the time didn’t say much on that subject. With the whole team focused on quality and testing, we came up with some great solutions. I was so excited about XP testing that I co-authored a book on it (Testing Extreme Programming, with Tip House).

Read More... | 22044 bytes more
Book : Competitive Engineering by Tom Gilb
on 2007/9/13 3:18:45 (1214 reads)
Book

In a period where the trend is to follow agile approaches with condensed guidance (see the 12 principles of the Agile Manifesto for instance), it could seem strange to publish a book on software development with more than 500 dense pages. You should however not be frightened by this book. Beneath the size and the structured form lies an approach based on practical experience that incorporates change and flexibility without abandoning the quest for precision and delivering value.

Read More... | 3681 bytes more
News : Doctor Beck and Mister Dilbert
on 2007/9/12 5:47:28 (1343 reads)
News

Following a dzone.com link, I reached an article accompanying a presentation made by Joe Rainsberger at the Agile 2007 conference. This article, "My Greatest Misses: XP 2000-2007", is an honest experience report on the many issues and failures met by Joe Rainsberger as an agile change agent during these years, trying to teach others the merit of the extreme programming approach created by Kent Beck.

Read More... | 3255 bytes more
Articles : Using Customer Tests to Drive Development
on 2007/9/7 2:56:36 (1445 reads)
Articles

Like many agile software development teams, our team writes tests for each feature before the feature is actually developed. We’ve found many advantages to using tests to drive development, not only at the unit test level but at the functional, system and acceptance test levels. Not only do we have tests which show whether we’ve delivered the correct functionality, but we benefit from increased communication and collaboration, increasing the chances that we will deliver exactly what our customers want. Writing just the right amount of tests and level of detail has proved difficult at times, as has the automation and timing of the automation effort. The effort to overcome those problems has paid off and led us to devote even more resources to driving development with customer tests.

Read More... | 18501 bytes more
Quotes : XP Strategy
on 2007/9/7 2:33:33 (1262 reads)
Quotes

In XP, we don't divide and conquer. We conquer and divide. First we make something that works, then we bust that up and solve the little parts.


Kent Beck 

Book : Integrating Agile Development in the Real World by Peter Schuh
on 2007/9/7 2:27:37 (1427 reads)
Book

This book provides excellent material for a transition from a traditional approach to an agile method.

Read More... | 1276 bytes more
Articles : Agile Requirements
on 2007/8/31 7:34:16 (1173 reads)
Articles

In the last few years, the agile software development movement has created a paradigm shift in how we work to understand system requirements. Agile teams shape software systems using a collaborative process, with executable software at its heart and documents marginalised to a peripheral role. This creates a fundamental shift away from tools for managing requirements artefacts. Instead, we need tools that support collaboration and the gradual distillation of business rules into automated test suites.

Read More... | 21845 bytes more
« 1 ... 28 29 30 (31) 32 »
Share The Knowledge

Jobs