Search Results

I don't think the rest of the business is going to help because they have no sense of development life cycles, and requirements get changed all the time within a single sprint. One thing that bus …

Managing any documentation can be difficult regardless of whether you are using agile stories or a big up front document, and in order to reduce the burden, the documentation should be minimal and updated …

The skill isn't to write software without requirements. It is instead to elicit requirements from the project owner regardless of whether there is a formal requirements documentation or not. Gatherin …

Off the top of my head, here a just a few reasons why it is important to keep a log. If you wish to patent something you have invented, then a log book becomes a very vital piece of evidence. If you …

Also, the lack of documentation on an XP or an agile process to extend the OPs example should not be an issue for an agile process if the code is written to be readable, and the requirements have been … what I like to think of as a wrapper methodology, in that within the scope of the Develop/Test stages, the feature sets can be treated as mini-projects in themselves, and could be implemented using an Agile …

applied testing where a reluctance to stick with a test-driven process has seen developers fall back on old habits and do all of their testing at the end of the project (these same people claim to be Agile …

The comparison between Agile and any methodology is a false one. … It really is one thing to say "Ok, so now we are Agile", and totally another to actually live and work by the philosophy that Agile is. …

If all of this isn't Agile, I ask you what is? … So my answer is Yes, you can be an Agile Software Developer, and you can apply an Agile methodology, and you don't necessarily need the customer, or even the manager. …

A User Story is an informal statement in the language of the customer which captures the intent of something that the customer wishes to achieve. You can think of a User Story as an Informal Requirem …

Agile works just as well for individuals as it does for teams. … Agile processes are highly iterative. Work is done in short TimeBoxes/sprints/cycles/iterations. …

Having them receptive to the very idea of Agile is most of the battle. … Before your company decides anything, I would recommend getting in an Agile coach to do a half day seminar and workshop. …

Writing your own tests is very agile, and waiting for testers time to become available can be very wasteful. … Ultimately, being Agile is about finding a solution that works well for your team, your company, and your customers. …

Whether Agile works in any company all comes down to the mind-set of the the people working with it, how the team thinks about it, and how committed they are towards making an Agile methodology work for … It's about achieving a compromise between your vision of an agile workflow, and the existing business processes that may need to be modified to accommodate agile processes. …

In terms of a "pure" Agile approach, you allow your team to use any combination of tools and processes that works well for them. …