background preloader

Best Practices

Facebook Twitter

Declaration of Interdependence. The declaration of interdependence for modern management or DOI. The project/product management Declaration of interdependence was written in 2005 as an adjunct to the Agile Manifesto.

The declaration of interdependence for modern management or DOI

See also: Here is an explanation of it I wrote immediately upon returning from writing it “We … increase return on investment by — making continuous flow of value our focus.deliver reliable results by — engaging customers in frequent interactions and shared ownership.expect uncertainty and manage for it through — iterations, anticipation and adaptation.unleash creativity and innovation by — recognizing that individuals are the ultimate source of value, and creating an environment where they can make a difference.boost performance through — group accountability for results and shared responsibility for team effectiveness.improve effectiveness and reliability through — situationally specific strategies, processes and practices.”

The “Declaration of Interdependence” for modern (agile/adaptive) (product/project) management There’s even a logo to go with it ;-). 1. 2. 3. 4. Principles behind the Agile Manifesto. We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Principles behind the Agile Manifesto

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project.

Build projects around motivated individuals. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. Code Charts. Scripts | Symbols | Notes Find chart by hex code: Related links: Name index Help & links Scripts Symbols and Punctuation Notes To get a list of code charts for a character, enter its code in the search box at the top.

Code Charts

For terms of use, conventions used in this table, access to additional charts and ways to access the code charts, see Character Code Chart Help and Links. The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) By Joel Spolsky Wednesday, October 08, 2003 Ever wonder about that mysterious Content-Type tag?

The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)

You know, the one you're supposed to put in HTML and you never quite know what it should be? Did you ever get an email from your friends in Bulgaria with the subject line "???? ?????? I've been dismayed to discover just how many software developers aren't really completely up to speed on the mysterious world of character sets, encodings, Unicode, all that stuff. But it won't. So I have an announcement to make: if you are a programmer working in 2003 and you don't know the basics of characters, character sets, encodings, and Unicode, and I catch you, I'm going to punish you by making you peel onions for 6 months in a submarine. And one more thing: In this article I'll fill you in on exactly what every working programmer should know. A Historical Perspective The easiest way to understand this stuff is to go chronologically. And all was good, assuming you were an English speaker.

Unicode Hello Encodings.