
	Where results make sense

Topic: Alistair Cockburn

Related Topics

Alexander Cockburn

Alexander Cockburn Lord Chief Justice

Patrick Cockburn

Andrew Cockburn

George Cockburn

Claud Cockburn

James Cockburn

Cockburn Town

Richard Cockburn Maclaurin

Douglas Cockburn Frith

John Cockburn

In the News (Wed 9 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Software Dioxide: Use Cases, Ten Years Later (Site not responding. Last check: 2007-10-16)
		Cockburn says that we need to mark the use case with the relative size of the goal it is capturing so that the reader is alert about what the writer was thinking and this will save a great deal of miscommunication.
		Cockburn describes an incident where analysis done by listing all stakeholders and their interests for a system that had been shipped recently showed up most of the changes that had come in as change requests in the first year of operation.
		Cockburn says that as this model became accepted, it was still not formal enough for formalists, yet it was too formal and required too much writing for those who liked to think of use cases as informal, unstructured, non-requirements description.
	www.softwaredioxide.com /Channels/ConView.asp?id=6845 (1541 words)

	Ian Alexander's Reviews of Books on Requirements Engineering and Related Subjects - Cockburn on Use Cases
		Cockburn points out some of the difficulties, accepts that they are here to stay, and works around them by concentrating mainly on use case text.
		Cockburn organises use case text in many ways, supplementing it with icons to indicate fl or white box views and level (high in the clouds, up with a flying kite, at the user-level ocean surface, underwater with the fishes, or 'too low' down amongst the clams).
		Cockburn's perspective is admittedly that of a skilled developer, but he is aware that other people who are not developers exist and matter, and that system scope is a critical point of agreement.
	i.f.alexander.users.btopenworld.com /reviews/cockburn.htm (1007 words)

	IT Conversations: Alistair Cockburn - Agile Software Development
		Alistair Cockburn had been a hardware designer and researcher for 16 years when IBM asked him to write a methodology for object-oriented projects.
		Alistair explains how Agile is different from XP (eXtreme Programming) and talks about his forthcoming book on Crystal Clear, his answer to XP.
		Cockburn does a terrific job of blending experience, anecdotal evidence, cited references, interviews, figures, analogies, and humor.
	www.itconversations.com /shows/detail175.html (565 words)

	Software Dioxide: Learning From Agile Software Development — Part One (Site not responding. Last check: 2007-10-16)
		Cockburn starts with the first principle — different projects need different methodology tradeoffs, and says that while this is obvious, it often needs restating.
		Cockburn quotes a study to say that physical distance matters a great deal, and discusses the aspect of costs such as salary to say that the loss of not communicating is higher than the cost of communicating.
		Cockburn concludes this first part article with a summary where he emphasizes that teams should use the principles as slider scales and decide on their priorities.
	www.softwaredioxide.com /Channels/ConView.asp?id=7107 (541 words)

	Amazon.com: Books: Agile Software Development (Site not responding. Last check: 2007-10-16)
		Cockburn begins with the premise that communication is never perfect or complete - and therefore one task of your methodology, which amounts to the set of conventions your team follows, is to ensure that communications are optimal for the purposes at hand.
		Cockburn adeptly uses the metaphor of game theory to accurately characterize software development as "a cooperative game of invention and communication", whose primary goal is to deliver useful, working software, and whose secondary goal is to prepare for continued play.
		Cockburn was party to the meeting and the manifesto, and in the first appendix provides his own report on the meeting and interpretation of the group's values and principles.
	www.amazon.com /exec/obidos/tg/detail/-/0201699699?v=glance (2912 words)

	SS > NF reviews > Alistair Cockburn
		Cockburn discusses various tools that can be used when constructing use cases -- from the derided diagramming tools to a word processor with hyperlinks.
		Cockburn shows how the cooperative game idea gives insight into how teams work, how the agile methodologies should work, and how and why to tailor a given approach to a given project.
		Cockburn stresses there is no "one size fits all" project methodology -- except maybe at the meta-level.
	www-users.cs.york.ac.uk /susan/bib/nf/c/cockburn.htm (605 words)

	Alistair Cockburn is consulting fellow at Humans and Technology (Site not responding. Last check: 2007-10-16)
		Cockburn was special advisor to the Central Bank of Norway, advising on project management and development issues, object-oriented design and requirements gathering.
		Cockburn wrote handbooks on OO techniques and established coding standards for Smalltalk and C++.
		Cockburn was asked to orchestrate project setup and requirements for a corporate project in which few of the team of 40 had object technology experience.
	members.aol.com /acockburn/wwwbio.html (603 words)

	First eWorkshop on Agile Methods
		Alistair Cockburn disagreed with the statement proposed by the moderator that only considered part of the original statement.
		Alistair Cockburn’s opinion is: "How agile can we be, given that this is going to be critical, reliable, safe?" The answer will give strategies that will involve reviews, tests, interface simulators, etc., AND ALSO drive up the collaboration and morale components, since they will be equally crucial on such a project.
		Alistair Cockburn added that they may ignore the data from experiments, but if you don’t have data, they will ignore you.
	fc-md.umd.edu /projects/Agile/Summary/SummaryPF.htm (4614 words)

	Writing Effective Use Cases, Addison-Wesley Professional, Alistair Cockburn
		Alistair Cockburn's Writing Effective Use Cases is an approachable, informative, and very intelligent treatment of an essential topic of software design.
		But few comes as close as Alistair Cockburn's book in discussing Use Cases from practical experiences.Developing Use Cases is not a difficult concept to grasp - it is the part which heavily involves the client and is one of the most critical moments in the software development lifecycle.
		Cockburn's book gives excellent guidelines in the practical nature of Use Case development which tend to be omitted in most other books.
	allentech.net /bookstore/item_0201702258.html (1326 words)

	JAOO2000
		Alistair Cockburn will provide us with a 1/2 day tutorial: "Designing a Light Methodology", which was rated the top tutorial at OOPSLA in 1998.
		Alistair will show a framework for describing methodologies, so that you can start see some of the issues in customizing a process.
		Alistair Cockburn (pronounced "Coburn"), founder of Humans and Technology, designed the OO methodology for the IBM Consulting Group in the early-1990s, and was special advisor to the Central Bank of Norway.
	www.jaoo.dk /jaoo2000/conference/speakers/cockburn.html (263 words)

	Alistair Cockburn: Cutter Consortium Consultant
		Alistair Cockburn is a Senior Consultant with Cutter Consortium's Agile Software Development and Project Management Practice and a contributor to that Advisory Service.
		Cockburn was special advisor on project management and development issues to the Central Bank of Norway.
		Cockburn has developed courses in project survival, methodology development, requirements writing, OO design, and project management strategies.
	www.cutter.com /consultants/cockburna.html (1941 words)

	Alistair Cockburn - Agile Software Development (Site not responding. Last check: 2007-10-16)
		Alistair Cockburn: Yeah, well, I think it’s best that I obviously have not gotten anywhere near the bottom of this particular issue.
		Alistair Cockburn: Well, you bring up a thing that’s relevant, which is that reuse isn’t free.
		Alistair Cockburn: Well, the XP is just one of them, is the answer.
	www.itconversations.com /transcripts/175/transcript-print175-1.html (6102 words)

	Crystal Clear : A Human-Powered Methodology for Small Teams (Agile Software Development Series) by Alistair Cockburn (Site not responding. Last check: 2007-10-16)
		In this book Cockburn takes the reader by the hand, shares his deep insight in people-centric software development and give precise instructions and advise on how to run sofware projects with communication and human values as the base.
		Cockburn learns us, that most work products makes the biggest difference in the project, if they are made on the walls on whiteboards or stickers - as opposed to the usual way where work products are made on computer screens and saved (or "hidden") on server disk drives...
		Alistair Cockburn has presented 7 prinicples that assure software development is a human-based enterprise instead of a mechanical process.
	www.internetcross.com /item/0201699478 (755 words)

	Amazon.ca: Books: Surviving Object-Oriented Projects (Site not responding. Last check: 2007-10-16)
		Alistair Cockburn presents principles, patterns and case studies for managing projects that use object oriented techniques, choosing "just enough process" and separating hype from reality.
		Cockburn is very explicit in his descriptions of how complex the move is and how valuable training can be, as well as the many inherent limitations that it has.
		Cockburn clearly has a great deal of consulting experience in helping people make the transition and he passes that on using a very readable style.
	www.amazon.ca /exec/obidos/ASIN/0201498340 (1052 words)

	JavaRanch Big Moose Saloon: Incremental vs Iterative (Site not responding. Last check: 2007-10-16)
		An increment could be widely varying in size, from a new method in a class all the way up to a multi-class subsystem, and therefore may or may not need to be 'project managed'.
		Yes, each imcrement is likely developed iteratively, but as Alistair didn't quite clarify is that there is a difference between purposely developing incrementally/iteratively/both (ie, planning for it) and developing same randomly (subconsciously??) in an unplanned manner.
		This is an almost impossible desire to fulfill, so having something so simple as the three levels in the, and having that make such a big difference, is triply rewarding.
	saloon.javaranch.com /cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=42&t=000161 (1487 words)

	Amazon.co.uk: Books: Writing Effective Use Cases (Site not responding. Last check: 2007-10-16)
		In Writing Effective Use Cases, Alistair Cockburn offers a hands-on, soup-to-nuts guide to use case development, based on the proven concepts he has refined through years of research, development, and seminar presentations.
		Cockburn shows how use cases fit together with requirements gathering, business processing reengineering, and other key issues facing software professionals.
		I have read a number of UML books in the past and nearly all of them have passed off Use Case writing with a sentence like "A complete discussion of this is a topic for a whole other book." Well this is the other book.
	www.amazon.co.uk /exec/obidos/ASIN/0201702258 (1526 words)

	DBLP: Alistair Cockburn
		Alistair Cockburn: A Formalization of Temporal Message-Flow Diagrams.
		Alistair Cockburn, Wayne Citrin, Rainer Hauser, Jürg von Känel: An environment for interactive design of communications architectures.
		Alistair Cockburn: Efficient implementation of the OSI protocol checksum algorithm using 8/16-bit arithmetic.
	www.informatik.uni-trier.de /~ley/db/indices/a-tree/c/Cockburn:Alistair.html (240 words)

	[No title] (Site not responding. Last check: 2007-10-16)
		In this one of two anchors to the Agile Software Development Series, Alistair Cockburn presents his view: Software Development is a cooperative game.
		From this perspective, Cockburn builds a vocabulary that we can use to identify with and learn from experiences and observations that he and other practitioners of agile methodologies such as XP, Crystal, Adaptive, Scrum, and FDD have shared throughout their careers.
		This book has me convinced that Cockburn’s view comes very close to describing the true nature of the huge and complex beast that is Software Development.
	www.javaranch.com /newsletter/Apr2002/bookreview.html (240 words)

	Agile Software Development
		Lightweight methodologies are exploding in popularity because their flexibility is ideal for today's fast-changing development environments.
		In Agile Software Development, legendary software expert Alistair Cockburn reviews the advantages and disadvantages of lightweight methods, synthesizing the field's key lessons into a simplified approach that allows developers to focus on building quality software rapidly, cost-effectively, and without burnout.
		Modifying an existing methodology is easier than creating a new one and is more effective than using one that was designed for a different situation.
	www.businessanalysisbooks.com /0201699699.html (2793 words)

	Alistair Cockburn: Surviving Object-Oriented Projects (Agile Software Development Series)
		Key points are supported and illustrated through short case studies taken from real object-oriented projects, and an appendix collects these workable guidelines and solutions into brief "crib sheets"- ideal for handy reference.
		While books on software engineering and project management abound, Alistair Cockburn's Surviving Object-Oriented Projects stands out as a lively view from the trenches of project management.
		It provides plenty of tips and tricks that will help you avoid the most common hazards of working with objects, especially for the first time.
	book-aholic.com /ASIN0201498340.htm (459 words)

	Use Case Alternate Intro
		Alistair Cockburn Humans and Technology, 7691 Dell Rd, Salt Lake City, UT 84121 email: arc@acm.org
		This Use Case Fundamentals mini-document was sent by someone who had read the article "Structuring Use Cases with Goals", and wrote a digest of it for his group (thanks, Peter).
		The use cases in this report are generated using a goal oriented Structuring Methodology presented by Alistair Cockburn of Humans and Technology.
	members.aol.com /acockburn/papers/AltIntro.htm (1358 words)

	Alibris: Alistair Cockburn
		In "Writing Effective Use Cases, " Cockburn offers a hands-on, soup-to-nuts guide to use case development, based on the proven concepts he has refined through years of research, development, and seminar presentations.
		Simple, elegant, and proven solutions to the specific problems of writing use cases on real projects, this workbook has 36 specific guidelines that readers can use to measure the quality of their use cases.
		Author Alistair Cockburn distills the secrets shared by successful small teams on what works and doesn't work in their development processes.
	www.alibris.com /search/books/author/Alistair_Cockburn (320 words)

	Amazon.ca: Books: Agile Software Development (Site not responding. Last check: 2007-10-16)
		Over the years I've developed a good feel for how a great project runs, but have found it remarkably hard to communicate what it is that makes the difference between successful and failed projects.
		I was delighted to find that Alistair Cockburn has worked out how to articulate the difference and how to make sure that your projects are the successful ones.
		While Brooks mostly emphasize that the term "man-month" can't be applied to software development, DeMarko and Lister focus to productive environment and jelled teams, Alistair Cockburn with the book "Agile Software Development" covers much wider area, including the choice of the right methodology, problems of individuals and aspects of communication.
	www.amazon.ca /exec/obidos/ASIN/0201699699 (1458 words)

	Marco Dorantes' WebLog : Crystal Clear:A Human-Powered Methodology for Small Teams by Alistair Cockburn
		I have found this book useful because of the level of detail and remarkable objective view about the aspects of methodology that works, that is to say, people-orientation.
		Alistair’s previous publications about methodology space convey the depth of what methodology entails [2], and what is to be considered for such methodology customization; somewhat recently, his publications focus on particular customizations becoming a ‘methods family’ called Crystal.
		The best thing about Cockburn's work, imho, is the emphasis of s/w dev as a co-operative game.
	blogs.msdn.com /marcod/archive/2005/03/07/388732.aspx (298 words)

	Amazon.co.uk: Books: Agile Software Development: Software Through People (Site not responding. Last check: 2007-10-16)
		Cockburn has a very succinct style with clear illustrations to support his explanations that I have re-used in my presentations (along with others in his other books).
		He explains the building blocks of software methodologies and what makes some work more than others and explains why one methodology does not fit all projects and how and where each one must be shaped to fit the size of the project.
		Mr Cockburn has really hit the nail on the head with this book, and it's easy to read.
	www.amazon.co.uk /exec/obidos/ASIN/0201699699 (1159 words)

	benjaminm's blog - Notes from Alistair Cockburn's PhD thesis
		Recently I've been reading Alistair Cockburn's PhD thesis People and Methodologies in Software Development.
		He argues that people are more important than methodology, there's no one methodology that will always be right (and there will always be new ones coming along) and that successful teams create their own methodology based on the needs of the project and the people involved.
		Alistair's quote 'A common answer to asking why a project succeeded at all is: "A few good people stepped in and did whatever was needed to get the job done."'.
	benjaminm.net /PermaLink.aspx?guid=1da3b646-5e77-49d9-8c8e-cde0c88ff41d (853 words)

	AgileAlliance (Site not responding. Last check: 2007-10-16)
		Alistair explains how he uses games as a model for software projects, and how he discovered that the term "software engineering" was created on a whim in 1968.
		An interesting interview of Alistair Cockburn, featuring an anecdote about using agile techniques to make changes in a business environment, followed by some thoughts on when and when not to use agile techniques in projects.
		Also included are lengthy sidebars on Crystal (by Alistair Cockburn) and Refactoring (by Ken Orr).
	www.agilealliance.org /articles/searchResults?topic=Crystal (220 words)

	Crystal Main Foyer
		However, Jim and Alistair will both contribute and continue to merge their insights about principles and practices for running a project as fast and effectively as the circumstances permit.
		This site is a resource for people wanting to understand those ideas, to find more about improving skills and teaming, and to identify some project policies to use as a starting point.
		This site was set up by Alistair Cockburn (name pronounced "Coburn"), Jim Highsmith, Kay Johansen (Perl engines) and Mike Jones (graphic design).
	alistair.cockburn.us /crystal/crystal.html (414 words)

	SD Best Practices 2004 (Site not responding. Last check: 2007-10-16)
		Alistair Cockburn is an internationally respected expert on object-oriented design, software development methodologies, use cases and project management.
		Cockburn defined an early agile methodology for the IBM Consulting Group in 1992, served as special advisor to the Central Bank of Norway in 1998, and has worked in companies from Scandinavia to South Africa, North America to China.
		Internationally, he is known for his seminal work on methodologies and use cases, as well as his lively presentations and interactive workshops.
	www.cmpevents.com /SDe4/a.asp?option=G&V=3&id=229666 (384 words)

Try your search on: Qwika (all wikis)