Linda Rising

Last updated

Linda Rising is an American author, lecturer, independent consultant. Rising is credited as having played a major role in having "moved the pattern approach from design into corporate change." [1] She also contributed to the book 97 Things Every Software Architect Should Know, edited by Kevlin Henney and published by O´Reilly in 2009 ( ISBN   059652269X).

Contents

University education

In 1964, Rising obtained a bachelor's degree in chemistry at the University of Kansas, in 1984 a Master of Science degree in computer science at Southern Illinois University and in 1987 a M. A. in mathematics at the Southwest Missouri State University. In 1992, Rising obtained her PhD degree in computer science from the Arizona State University, with her thesis entitled Information hiding metrics for modular programming languages relating to object-based design metrics. [2] [3]

Teaching

Rising taught as instructor in mathematics and computer science at various universities throughout the midwest from 1977 to 1984 and worked as assistant professor from 1984 to 1987 at Indiana University – Purdue University Fort Wayne. [2]

Industry, consulting and writing

In industry, she worked in the areas of telecommunications, avionics, and tactical weapons systems. [4]

Rising has extended the use of patterns, building upon the work of Christopher Alexander on a pattern language for architecture and the work of the Gang of Four on patterns for software development. She extended the use of patterns to the support of organisational change. Her work and lectures cover patterns, retrospectives, agile development approaches and the change process, [5] topics on which she is an internationally known lecturer. [4]

Since 2010, she is editor of the Insights series of the IEEE Software magazine. [6]

Her book The Pattern Almanac 2000 provides a comprehensive inventory of patterns compiled from publications in patterns conferences and books prior to the year 2000. [7] [8] The patterns are listed by name and divided into categories, and for each pattern a rudimentary description as well as a reference to a book, journal or URL where the actual published pattern can be found is provided. [9] The Pattern Almanac 2000 has been cited as reference on existing patterns [7] and used as starting-point of further research. [10] Rising's indexing of existing patterns is seen as "a significant start toward achieving the ultimate goal of a pattern database." [11]

The study The scrum software development process for small teams by Rising and Norman S. Janoff is cited as first published study in which the scrum, a development process for small teams which includes a series of "sprints" which each last typically between one and four weeks, [12] [13] was tested in real-life projects. [14] The study has been cited for showing "that nonhierarchical teams work more effectively through the complex iterations and time-consuming gestation of a software program" and that "they gain strength through shared successes and failures". [15]

She is editor of the book Design Patterns in Communication Software, a compendium of patterns, which appeared 2001. Contributors to her book include experts from the patterns community such as James O. Coplien and Douglas C. Schmidt. [16] She is author of Fearless Change: Patterns for Introducing New Ideas, co-authored with Mary Lynn Manns and published 2004. [17]

Rising has been keynote speaker at the agile 2007 conference (topic: "Are agilists the bonobos of software development?"), [18] the OOP 2009 conference (topic: "Who Do You Trust?"), [19] the Agile testing days Berlin 2010 (topic: "Deception and Estimation: How we fool ourselves"), [20] at the GOTO Amsterdam 2014 conference (topic: "Science or Stories?"), [21] and at the European Testing Conference 2016 in Bukarest (topic: "The Agile Mindset") [22]

Her work has inspired many in the agile community, for instance Steve Adolph and Paul Bramble, who, together with Alistair Cockburn and Andy Pols, expanded further on Rising's use patterns. [23]

Rising lives in Phoenix, Arizona.

Books

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 public speaker

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.

In computer programming and software design, code refactoring is the process of restructuring existing computer code—changing the factoring—without changing its external behavior. Refactoring is intended to improve the design, structure, and/or implementation of the software, while preserving its functionality. Potential advantages of refactoring may include improved code readability and reduced complexity; these can improve the source code's maintainability and create a simpler, cleaner, or more expressive internal architecture or object model to improve extensibility. Another potential goal for refactoring is improved performance; software engineers face an ongoing challenge to write programs that perform faster or use less memory.

<span class="mw-page-title-main">Software architecture</span> High level structures of a software system

Software architecture is the set of structures needed to reason about a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.

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.

<span class="mw-page-title-main">Grady Booch</span> American software engineer

Grady Booch is an American software engineer, best known for developing the Unified Modeling Language (UML) with Ivar Jacobson and James Rumbaugh. He is recognized internationally for his innovative work in software architecture, software engineering, and collaborative development environments.

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.

<span class="mw-page-title-main">Craig Larman</span> Canadian-born computer scientist, author, and organizational development consultant

Craig Larman is a Canadian computer scientist, author, and organizational development consultant. With Bas Vodde, he is best known for formulating LeSS, and for several books on product and software development.

<span class="mw-page-title-main">Ivar Jacobson</span>

Ivar Hjalmar Jacobson is a Swedish computer scientist and software engineer, known as a major contributor to UML, Objectory, Rational Unified Process (RUP), aspect-oriented software development and Essence.

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

Scrum is an agile team collaboration framework commonly used in software development and other industries.

<span class="mw-page-title-main">Alistair Cockburn</span> American computer programmer

Alistair Cockburn is an American computer scientist, known as one of the initiators of the agile movement in software development. He cosigned the Manifesto for Agile Software Development.

The bus factor is a measurement of the risk resulting from information and capabilities not being shared among team members, derived from the phrase "in case they get hit by a bus". It is also known as the bus problem, truck factor, or bus/truck number.

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.

Douglas C. Schmidt is a computer scientist and author in the fields of object-oriented programming, distributed computing and design patterns.

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.

<span class="mw-page-title-main">Tim Lister</span>

Tim Lister is an American software engineer and author with specialty in design, software risk management, and human aspects of technological work. He is a Principal of The Atlantic Systems Guild Inc. and a fellow of the Cutter Consortium.

<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.

References

  1. Preston G. Smith: Flexible product development: building agility for changing markets, John Wiley & Sons, 2007, ISBN   978-0-7879-9584-3, p. 245
  2. 1 2 Linda Rising Archived 2009-04-01 at the Wayback Machine at cox.net
  3. Linda Rising on Customer Interaction Patterns, Interview with Linda Rising by Dan Puckett on December 29, 2010
  4. 1 2 Linda Rising at: Meetup - OpenSource & Agile Community Events
  5. Linda Rising Archived 2012-05-13 at the Wayback Machine , QCon
  6. Linda Rising: Telling Our Stories, IEEE IEEE Software Computer Society, May/June 2010, pp. 6-7 (available online from her homepage)
  7. 1 2 Gunter Mussbacher, Daniel Amyot, Michael Weiss: Formalizing patterns with user requirements notation, In: Toufuk Taibi: Design patterns formalisation techniques, IGI Publishing, ISBN   978-1-59904-219-0, p. 302-323, Page: 315
  8. Aliaksandr Birukou, Enrico Blanzieri, Paolo Giorgini: Facilitating Pattern Repository Access with the Implicit Culture Framework, DOI 10.1.1.77.2404, p. 1
  9. A directory of patterns Archived 2011-07-07 at the Wayback Machine (book review)
  10. C. Larman: Protected variation: the importance of being closed, IEEE Software, May 2001, Volume 18, Issue No. 3, pp. 89-91, DOI 10.1109/52.922731
  11. Sherif M. Yacoub, Hany Hussein Ammar: Pattern-oriented analysis and design: composing patterns to design software systems, Addison-Wesley, 2003, ISBN   0-201-77640-5, p. 115
  12. Linda Rising, Norman S. Janoff: The scrum software development process for small teams, IEEE Software, Volume 17 Issue 4, July 2000, IEEE Computer Society Press, doi : 10.1109/52.854065, p. 6 Archived 2010-08-21 at the Wayback Machine
  13. Torgeir Dingsøyr, Geir Kjetil Hanssen, Tore Dybå, Geir Anker, Jens Olav Nygaard: Developing Software with Scrum in a Small Cross-Organizational Project, R. Messnarz (Ed.): EuroSPI 2006, LNCS 4257, pp. 5–15, 2006, p. 6
  14. Pekka Abrahamsson, Juhani Warsta, Mikko T. Siponen and Jussi Ronkainen: "New Directions on Agile Methods: A Comparative Analysis", Proceedings of the International Conference on Software Engineering, May 3–5, 2003
  15. Louis M. Abbey, Pamela Arnold, Lucy Halunko, Mary Beth Huneke, Stacie Lee: "Case studies for Dentistry: Development of a tool to author interactive, multimedia, computer-based patient simulations", Journal of Dental Education, December 2003, pp. 1345–1354, p. 1347
  16. Design patterns in communication software, Cambridge University Press
  17. Nicolai M. Josuttis: SOA in practice: The art of distributed system design, O´Reilly, 2007, ISBN   978-0-596-52955-0, p. 276
  18. Agile 2007 Archived 2011-07-27 at the Wayback Machine
  19. OOP 2009, Program (in German language)
  20. Agile testing days in Berlin, a report in German language
  21. GOTO Amsterdam 2014 conference schedule
  22. conference schedule
  23. Steve Adolph, Paul Bramble, with contributions by Alistair Cockburn, Andy Pols: Patterns for effective use cases, Addison-Wesley, 2003, ISBN   0-201-72184-8, section Pattern Language Heritage