Search everyone's bookmarks
[Spam reported - thank you]
http://www.codeproject.com/gen/design/scrum.asp
C++ (VC7.1, VC7, VC6), MC++, C#, VB.NET Windows (WinXP, Win2K, Win2003, Win95, Win98, WinME), .NET (.NET 1.1, .NET 1.0) ASP.NET, ASP, Win32, VS Dev Posted
...
: 19 Aug 2003 Views : 131,296 My main goal as a developer is to improve the way software is designed, and how it interacts with the user. I like designing software best, but I also like coding and documentation. I especially like to work with user interfaces and graphics. I have extensive knowledge of the .NET Framework, and like to delve into its internals. I specialize in working with VG.net and MyXaml. I also like to work with ASP.NET, AJAX, and DHTML (it's nice except when inconsistencies and bugs make me want to tear my hair out!). I am currently looking for contract work. My resume and contact info can be found here . Click here to view J. Dunlap's online profile. As software developers, piracy is something that affects us all. If you are a software developer who works for a big company, you do not see it directly, but you stil
[More...]
[Less...]
Average rating (1 rating):
http://martinfowler.com/articles/newMethodology.html
Probably the most noticeable change to software process thinking in the last few years has been the appearance of the word 'agile'. We talk of agile software
...
methods, of how to introduce agility into a development team, or of how to resist the impending storm of agilists determined to change well-established practices.
This new movement grew out of the efforts of various people who dealt with software process in the 1990s, found them wanting, and looked for a new approach to software process. Most of the ideas were not new, indeed many people believed that much successful software had been built that way for a long time. There was, however, a view that these ideas had been stifled and not been treated seriously enough, particularly by people interested in software process.
This essay was originally part of this movement. I originally published it in July 2000. I wrote it, like most of my essays, as part of trying to understand the topic. At that time I'd used Extreme Programming for
[More...]
[Less...]
Average rating (1 rating):
http://www.martinfowler.com/articles/continuousIntegration.html
is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to
...
multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. This article is a quick overview of Continuous Integration summarizing the technique and its current usage. Last significant update: 01 May 06 ThoughtWorks , my employer, offers consulting and support around Continuous Integration in general, and CruiseControl in particular. We originated CruiseControl and have always had active committers on each of the projects. We are also beginning to develop a proprietary add-on to CruiseControl that's suitable for large enterprise environments; although we are committed to supporting and enhancing the co
[More...]
[Less...]
Average rating (0 ratings):
http://www.scopemanagement.co.uk
scopemanagement.co.uk
Average rating (2 ratings):
http://steve-yegge.blogspot.com/2006/09/good-agile-bad-agile_27.html
When I was growing up, cholesterol used to be bad for you. It was easy to remember. Fat, bad. Cholesterol bad. Salt, bad. Everything, bad. Nowadays, though,
...
they differentiate between "good" cholesterol and "bad" cholesterol, as if we're supposed to be able to distinguish them somehow. And it was weird when they switched it up on us, because it was as if the FDA had suddenly issued a press release announcing that there are, in fact, two kinds of rat poison: Good Rat Poison and Bad Rat Poison, and you should eat a lot of the Good kind, and none of the Bad kind, and definitely not mix them up or anything.
Up until maybe a year ago, I had a pretty one-dimensional view of so-called "Agile" programming, namely that it's an idiotic fad-diet of a marketing scam making the rounds as yet another technological virus implanting itself in naive programmers who've never read "No Silver Bullet", the kinds of programmers who buy extended warranties and self-help books and believe their bosses genuin
[More...]
[Less...]
Average rating (2 ratings):
http://agilemanifesto.org/
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions
...
over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
[More...]
[Less...]
Average rating (1 rating):
http://en.wikipedia.org/wiki/Agile_software_development
Agile software development is a conceptual framework for software engineering that promotes development iterations throughout the life-cycle of the project.
...
There are many agile development methods; most minimize risk by developing software in short amounts of time. Software developed during one unit of time is referred to as an iteration, which may last from one to four weeks. Each iteration is an entire software project: including planning, requirements analysis , design, coding, testing , and documentation. An iteration may not add enough functionality to warrant releasing the product to market but the goal is to have an available release (without bugs) at the end of each iteration. At the end of each iteration, the team re-evaluates project priorities.
Agile methods emphasize face-to-face communication over written documents. Most agile teams are located in a single open office sometimes referred to as a bullpen. At a minimum, this includes programmers and their "customers" (cust
[More...]
[Less...]
Average rating (1 rating):
http://www.agilemodeling.com/essays/introductionToAM.htm
The Elements of UML 2.0 Style describes a collection of standards, conventions, and guidelines for creating effective UML diagrams . They are based on
...
sound, proven software engineering principles that lead to diagrams that are easier to understand and work with. These conventions exist as a collection of simple, concise guidelines that if applied consistently, represent an important first step in increasing your productivity as a modeler. This book is oriented towards intermediate to advanced UML modelers, although there are numerous examples throughout the book it would not be a good way to learn the UML (instead, consider The Object Primer ). The book is a brief 188 pages long and is conveniently pocket-sized so it's easy to carry around.
[More...]
[Less...]
Average rating (1 rating):
Tags:
agile,
aup,
development,
dsdm,
extreme
,
fdd,
modeling,
programming,
rup,
software,
xp
[More...]
[Less...]
[Report as spam]
[Report as spam]
