Mike Cohn

Last updated
Mike Cohn
WEB RES-Mike Cohn-(c)-2016-Hows Your Headshot-6.jpg
Born (1962-08-25) August 25, 1962 (age 61)
Anaheim, California, U.S.
Education
Known forFounder of Scrum Alliance
SpouseLaura Cohn

Mike Cohn (born August 25, 1962) is one of the contributors to the Scrum software development method. [1] He is one of the founders of the Scrum Alliance. [2]

Contents

Early life and education

Born in Anaheim, California, U.S. in 1962, Mike Cohn received his master's degree in computer science from the University of Idaho in northern Idaho. [3] Having a research interest in Agile project management, he specializes in communicating needs and achieving Agile project goals through user stories. [4]

Career

Cohn began his career in the early 1980s as a programmer in APL and BASIC before moving on to C++ and Java and running development groups. [5]

Cohn is the founder of Mountain Goat Software, a process and project management consultancy and training firm. [6] He is the author of Agile Estimating and Planning, User Stories Applied for Agile Software Development and Succeeding with Agile: Software Development using Scrum, as well as books on Java and C++ programming. [7] Cohn was a keynote speaker on ADAPTing to Agile for Continued Success at the Agile 2010 Presented by the Agile Alliance. [8] In 2012, Cohn was named #1 in The Top 20 Most Influential Agile People. [9]

Cohn is a proponent of stand-up meeting, particularly emphasizing actual standing during them. [10] Teams are encouraged to come up with their own rules for improving these meetings, for example fining people who are late to them. A 2011 survey of tech employees from around the world found that 78% held daily stand-up-meetings. [11]

Publications

Related Research Articles

<span class="mw-page-title-main">Kent Beck</span> American software engineer

Kent Beck is an American software engineer and the creator of extreme programming, a software development methodology that eschews rigid formal specification for a collaborative and iterative design process. Beck was one of the 17 original signatories of the Agile Manifesto, the founding document for agile software development. Extreme and Agile methods are closely associated with Test-Driven Development (TDD), of which Beck is perhaps the leading proponent.

<span class="mw-page-title-main">Martin Fowler (software engineer)</span> American software developer, author and international public speaker on software development

Martin Fowler is a British software developer, author and international public speaker on software development, specialising in object-oriented analysis and design, UML, patterns, and agile software development methodologies, including extreme programming.

<span class="mw-page-title-main">Anders Hejlsberg</span> Danish software engineer (born 1960)

Anders Hejlsberg is a Danish software engineer who co-designed several programming languages and development tools. He was the original author of Turbo Pascal and the chief architect of Delphi. He currently works for Microsoft as the lead architect of C# and core developer on TypeScript.

In software engineering, a software design pattern is a general, reusable solution to a commonly occurring problem within a given context in software design. It is not a finished design that can be transformed directly into source or machine code. Rather, it is a description or template for how to solve a problem that can be used in many different situations. Design patterns are formalized best practices that the programmer can use to solve common problems when designing an application or system.

In software and systems engineering, the phrase use case is a polyseme with two senses:

  1. A usage scenario for a piece of software; often used in the plural to suggest situations where a piece of software may be useful.
  2. A potential scenario in which a system receives an external request and responds to it.

In software development, agile practices include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/end user(s), Popularized in the 2001 Manifesto for Agile Software Development, these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban.

James O. Coplien, also known as Cope, is a writer, lecturer, and researcher in the field of computer science. He held the 2003–4 Vloeberghs Leerstoel at Vrije Universiteit Brussel and has been a visiting professor at University of Manchester.

In agile principles, timeboxing allocates a maximum unit of time to an activity, called a timebox, within which a planned activity takes place. It is used by agile principles-based project management approaches and for personal time management.

<span class="mw-page-title-main">Ken Schwaber</span> American computer scientist

Ken Schwaber is a software developer, product manager and industry consultant. He worked with Jeff Sutherland to formulate the initial versions of the Scrum framework and to present Scrum as a formal process at OOPSLA'95. Schwaber and Sutherland are two of the 17 initial signatories of the Agile Manifesto. They are co-authors of the Scrum Guide. Schwaber runs Scrum.org, which provides Scrum resources, training, assessments, and certifications for Scrum Masters, Scrum Developers, Scrum Product Owners, and organizations using Scrum.

In software development and product management, a user story is an informal, natural language description of features of a software system. They are written from the perspective of an end user or user of a system, and may be recorded on index cards, Post-it notes, or digitally in project management software. Depending on the project, user stories may be written by different stakeholders like client, user, manager, or development team.

<span class="mw-page-title-main">Scrum (software development)</span> Software development framework

Scrum is an agile project management system commonly used in software development and other industries.

Agile testing is a software testing practice that follows the principles of agile software development. Agile testing involves all members of a cross-functional agile team, with special expertise contributed by testers, to ensure delivering the business value desired by the customer at frequent intervals, working at a sustainable pace. Specification by example is used to capture examples of desired and undesired behavior and guide coding.

<span class="mw-page-title-main">Planning poker</span> Technique for estimating

Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating, mostly used for timeboxing in Agile principles. In planning poker, members of the group make estimates by playing numbered cards face-down to the table, instead of speaking them aloud. The cards are revealed, and the estimates are then discussed. By hiding the figures in this way, the group can avoid the cognitive bias of anchoring, where the first number spoken aloud sets a precedent for subsequent estimates.

Scott W. Ambler is a Canadian software engineer, consultant and author. He is an author of books about the Disciplined Agile Delivery toolkit, the Unified process, Agile software development, the Unified Modeling Language, and Capability Maturity Model (CMM) development.

Organizational patterns are inspired in large part by the principles of the software pattern community, that in turn takes it cues from Christopher Alexander's work on patterns of the built world. Organizational patterns also have roots in Kroeber's classic anthropological texts on the patterns that underlie culture and society. They in turn have provided inspiration for the Agile software development movement, and for the creation of parts of Scrum and of Extreme Programming in particular.

API testing is a type of software testing that involves testing application programming interfaces (APIs) directly and as part of integration testing to determine if they meet expectations for functionality, reliability, performance, and security. Since APIs lack a GUI, API testing is performed at the message layer. API testing is now considered critical for automating testing because APIs now serve as the primary interface to application logic and because GUI tests are difficult to maintain with the short release cycles and frequent changes commonly used with Agile software development and DevOps.

Specification by example (SBE) is a collaborative approach to defining requirements and business-oriented functional tests for software products based on capturing and illustrating requirements using realistic examples instead of abstract statements. It is applied in the context of agile software development methods, in particular behavior-driven development. This approach is particularly successful for managing requirements and functional tests on large-scale projects of significant domain and organisational complexity.

Acceptance test–driven development (ATDD) is a development methodology based on communication between the business customers, the developers, and the testers. ATDD encompasses many of the same practices as specification by example (SBE), behavior-driven development (BDD), example-driven development (EDD), and support-driven development also called story test–driven development (SDD). All these processes aid developers and testers in understanding the customer's needs prior to implementation and allow customers to be able to converse in their own domain language.

<span class="mw-page-title-main">Robert C. Martin</span> American software consultant

Robert Cecil Martin, colloquially called "Uncle Bob", is an American software engineer, instructor, and author. He is most recognized for promoting many software design principles and for being an author and signatory of the influential Agile Manifesto.

<span class="mw-page-title-main">Mike Beedle</span> American software engineer

Mike (Miguel) Beedle was an American theoretical physicist turned software engineer who was a co-author of the Agile Manifesto.

References

  1. ↑ Denning, Steve (2012-03-01). "The Power of Scrum". Forbes.
  2. ↑ "Mike Cohn". ScrumAlliance. Retrieved 2017-03-12.
  3. ↑ Cohn, Michael W. (1994). Empirical evaluation of a proposed set of complexity metrics for identifying defect prone classes in object-oriented programs (MS thesis). University of Idaho. OCLC   41823572.
  4. ↑ "Mike Cohn". ScrumAlliance.{{cite web}}: CS1 maint: url-status (link)
  5. ↑ "Video". InformIT. Archived from the original on 2012-01-14.
  6. 1 2 Cohn, Mike (2005-11-01). Agile Estimating and Planning. Prentice Hall.
  7. ↑ "Mike Cohn: Books, Biography, Blog, Audiobooks, Kindle" . Retrieved 2017-03-12.
  8. ↑ "Keynotes". Agile2010. Archived from the original on 2010-07-28. Retrieved 2017-03-12.{{cite web}}: CS1 maint: bot: original URL status unknown (link)
  9. ↑ Dolman, Paul (2012-04-01). "The top 20 most influential Agile people". Value, Flow, Quality. Retrieved 2017-03-12.
  10. ↑ "Hate those endless meetings? Try standing up". Marketplace.org. 2012-02-20. Retrieved 2017-03-12.
  11. ↑ "No More Angling for the Best Seat; More Meetings Are Stand-Up Jobs". The Wall Street Journal. 2012-02-02.
  12. ↑ Morgan, Bryan; Morrison, Michael; Nygard, Michael T.; Joshi, Dan; Trinko, Tom; Cohn, Mike (1996-11-01). Java Developer's Reference. SAMS.
  13. ↑ Hill, Kristy; Rutten, Jay; Gee, Mark; Moran, Jim; Cohn, Mike (1996-05-01). Database Developer's Guide With Borland C++5. SAMS.
  14. ↑ Cohn, Mike (1997-09-01). Teach Yourself Visual Cafe 2 in 21 Days. SAMS.
  15. ↑ Cohn, Mike; Rutten, Jay; Jory, James (1997-02-01). Web Programming With Visual J++. SAMS.
  16. ↑ Cohn, Mike (2004-03-01). User Stories Applied: For Agile Software Development. Addison-Wesley.
  17. ↑ Cohn, Mike (2009-10-26). Succeeding with Agile: Software Development Using Scrum. Addison-Wesley Professional.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.