TechnoBuzz

A Techno Blog, mainly about Java

CM is made of what?

http://devlicio.us/blogs/derik_whittaker/archive/2007/05/09/questions-every-candidate-should-ask-a-potential-new-employer.aspx

June 25, 2007 Posted by | Uncategorized | Leave a comment

Just Say No

“I am suggesting that there are those around us who are “serial committers” – they always say yes and rarely say no, even when they should.  These individuals become so engulfed by the shear number of commitments that they have made that it becomes impossible for them to execute on any of them, at least not effectively.”

http://cjhemp.wordpress.com/2007/04/28/promise-based-management/

June 25, 2007 Posted by | Uncategorized | Leave a comment

Practices are way to Go

http://drdobbs.com/dept/architect/198000264: “”

June 25, 2007 Posted by | Uncategorized | Leave a comment

Agile Software Process

AMIS on Deliver valuable software: “Other posts about the AGILE Principles soon to come:
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. (This one).
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity–the art of maximizing the amount of work not done–is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Forget those fancy tools, and try just enough information in requirement gathering.

June 8, 2007 Posted by | Patterns & UML, SW Tools, Web Design | Leave a comment