Skip to main content
Disciplines
Automotive Business IT + Informatics Construction + Real Estate Electrical Engineering + Electronics Energy + Sustainability Insurance + Risk Finance + Banking Management + Leadership Marketing + Sales Mechanical Engineering + Materials
Events
DE
EN
Books
Journals
Topic Page
Marketing
Start single access now
Access for companies
EXTENDED SEARCH
Log in
Top

2012 | Book

Software for People: A Paradigm Change in the Software Industry Read chapter Read first chapter

Software for People

Fundamentals, Trends and Best Practices

Editors: Alexander Maedche, Achim Botzenhardt, Ludwig Neer

Publisher: Springer Berlin Heidelberg

Book Series : Management for Professionals

Part of: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Login to get access
insite
SEARCH

About this book

The highly competitive and globalized software market is creating pressure on software companies. Given the current boundary conditions, it is critical to continuously increase time-to-market and reduce development costs. In parallel, driven by private life experiences with mobile computing devices, the World Wide Web and software-based services, peoples’ general expectations with regards to software are growing. They expect software that is simple and joyful to use. In the light of the changes that have taken place in recent years, software companies need to fundamentally reconsider the way they develop and deliver software to their customers.

This book introduces fundamentals, trends and best practices in the software industry from a threefold perspective which equally takes into account design, management, and development of software. It demonstrates how cross-functional integration can be leveraged by software companies to successfully build software for people. Professionals from business and academia give an overview on state-of-the-art knowledge and report on key insights from their real-life experience. They provide guidance and hands-on recommendation on how to create winning products. This combined perspective fosters the transfer of knowledge between research and practice and offers a high practical value for both sides.

The book targets both, practitioners and academics looking for successfully building software in the future. It is directed at Managing Directors of software companies, Software Project Managers, Product Managers and Designers, Software Developers as well as academics and students in the area of Software and Information Systems Engineering, Human Computer Interaction (HCI), and Innovation Management.​

Table of Contents

Frontmatter

Fundamentals and Trends

Frontmatter
Software for People: A Paradigm Change in the Software Industry
Abstract
The highly competitive and globalized software market is creating pressure on software companies. Given the current boundary conditions, it is critical to continuously increase time-to-market and reduce development costs. In parallel, driven by private life experiences with mobile computing devices, the World Wide Web and software-based services, peoples’ general expectations with regards to software are growing. They expect software that is simple and joyful to use. Given these boundary conditions, software companies need to fundamentally reconsider the way they develop and deliver software to their customers. This editorial article motivates the paradigm change towards “software for people”. We first illustrate in more detail the two important categories of challenges software companies are currently faced with. Building on a short review of the historic evolution of software, we explain the major reasons that caused these challenges. Driven by the more mature automotive industry, we outline a set of key principles that may help software companies to tackle these challenges. Finally, we summarize the structure and content of the book, building on these key principles and providing a comprehensive overview on fundamentals, trends and best practices for building software for people.
Alexander Maedche, Achim Botzenhardt, Ludwig Neer
User-Centered Design: Why and How to Put Users First in Software Development
Abstract
In this chapter we provide an overview of the activities and artefacts of the user-centered design (UCD) methodology – a successful and practical approach to the design of software user interfaces. After tracing its foundational principles (early focus on users, empirical measurement using prototypes and iterative design) back to 1985s seminal paper by Gould and Lewis, we will highlight each of five central categories of design activities (Scope, Analyse, Design, Validate and Deliver) performed in UCD. Potential integration of UCD into two popular categorizations of software development (User Interface First vs. User Interface Later) will be explored and then demonstrated in a real life case study from the field of electronic engineering along with a practical takeaway regarding the relationship of UCD and eLearning.
Dieter Wallach, Sebastian C. Scholz
Software Usability in Small and Medium Sized Enterprises in Germany: An Empirical Study
Abstract
Usability has become a competitive factor in the software industry. Specifically, the software industry in the United States has recognized this important factor and successfully leverages it for achieving competitive advantage. Compared to this fast development in the US, it seems questionable whether this view is also widespread among small and medium sized software producing and client companies in Germany and whether they direct sufficient attention to usability. This article presents the results of an empirical study exploring the status quo of the importance, the knowledge and the actual use of usability concepts among small and medium sized enterprises (SMEs) in Germany. Following an organizational field perspective, we investigate how interactions between actors in the software field influence the usability awareness as well as the knowledge and actual use of usability concepts. Based on the results of our study, we provide recommendations on how to increase awareness and maturity of software usability in SMEs in Germany.
Florian Scheiber, Dominika Wruk, Achim Oberg, Johannes Britsch, Michael Woywode, Alexander Maedche, Felix Kahrau, Hendrik Meth, Dieter Wallach, Marcus Plach
Software Product Management
Abstract
Software organizations evolve and maintain software solutions with more than a single development project. The delta specifications and artifacts that result from each project make reuse difficult and challenge a company’s ability to innovate. Software product management is a growing discipline for understanding how to productize and align software with company strategy, how to evolve software, and how to coordinate product stakeholders. With product focus, in addition to project focus, planning accuracy can be improved, time-to-market reduced, product quality enhanced, and economic success sustained. This chapter provides an overview on software product management and discusses what today is known about this discipline.
Samuel A. Fricker
Software Product Management and Agile Software Development: Conflicts and Solutions
Abstract
Agile software development has been established over the last 15 years as a popular development approach. In a time when speed of change is of utmost importance, agile approaches are often the most appropriate roads to success. They do not only change the way development is performed, but they also impact other parties involved in development projects, in particular the software product manager. Software companies are faced with the question how software product management and agile development can work together in an optimal way. Who is responsible for requirements? Is the software product manager automatically the designated “product owner” (Scrum)? Or is “product owner” a new and separate role? Does he/she replace the software product manager?
The Software Product Management Framework which has been developed by the International Software Product Management Association (ISPMA e.V., www.ispma.org) provides orientation. It can be used as a helpful tool to make the change process towards agile development successful.
Hans-Bernd Kittlaus
Requirements Engineering in Agile Software Development
Abstract
In all organization requirements engineering is applied at two different context levels: in the context of the product or service portfolio and in the context of projects. At the project context agile methods and techniques are often successfully established, although the discipline of requirements engineering often still is unattended. At the portfolio context agile techniques are hardly ever established thus leading to a culture clash between the portfolio and the project context. As requirements are the most important link of the chain from portfolios to projects, a solid and continuous agile approach in the discipline of requirements engineering from portfolio management level down into every single project is a key to open up unimagined potential for the organization. This article visualizes the forces behind agile techniques in requirements engineering, the “root causes” that interact and open up this potential. The understanding of these root causes enables individuals to implement the optimal version of agility in the organization.
Rainer Grau
Design Thinking: An Innovative Concept for Developing User-Centered Software
Abstract
In times of economic crisis and rapid technological change, innovation is necessary for competitive advantage and successful business. Design processes and tools are one way to create innovative solutions. This article describes the emergence of design thinking in business and focuses on the four key elements of design thinking in detail: the iterative process, multidisciplinary teams, creative space and designer’s mindset. The limitations and potentials of design thinking are also discussed. While design thinking enables creativity, enhances personal development, and prescribes deep immersion into the topic along with empathetic user research, it does not include a business model or blueprint for the implementation. Still, design thinking is a large step toward identifying user-centered solutions. The software industry can benefit from the powerful approach in order to create innovative software products.
Anja Wölbling, Kira Krämer, Clemens N. Buss, Katrin Dribbisch, Peter LoBue, Abraham Taherivand

Best Practices

Frontmatter
Best Practices for Successful Deployment of User Experience Design
Abstract
The pervasive use of technology in everyday life, at work, at home and while on the go increases the demand for easy to use systems, irrespective of platform or domain. Many companies recognize the need for successful deployment of user experience design (UXD) but still struggle to bring it to life in their product development. Best practices for integrating UXD into product development can help companies enhance the customer value of their products and services. They help product teams to collaborate more effectively and focus more on actual user needs. A set of simple, hands-on best practices can help UXD teams deliver their services more efficiently, effectively and to the satisfaction of not only the users, but also the participating product teams.
Kostanija Petrovic
Making Design Tangible in Software Development Projects
Abstract
User Experience (UX) Professionals often face the problem that their role and their contribution to software development projects are misunderstood. They are confronted with new challenges when they join agile or lean project teams. Over the following pages I will explain how UX professionals can make design tangible. I will describe how they can guide software development projects, how they can create a common understanding of the targeted User Experience and how they can involve others in the shaping of the design. After outlining the current challenges, I will explain how activities such as Design Studios, Sketching and Prototyping can be used to foster an understanding of the design rationale, and how artifacts like Product Vision Statements, Design Tenets, Personas, User Scenarios, Wireframes and UI Flows help to frame the design problem and document the design solution. Using these activities and artifacts will lead to smoother project operations and better results.
Lennart Hennigs
User Experience and User-Centered Design at DATEV eG
Abstract
DATEV eG products are not only convincing with technical and professional perfection, but also with a design that turns simple usage into a positive experience. In order to achieve the objective of a positive user experience, DATEV eG has long been focused on user-oriented development and user centered design respectively.
The following article offers you an insight into user experience and user centered design at DATEV eG today and points out important milestones on the way from technology-driven development to user centered design. We describe different challenges that needed to be addressed during the change and demonstrate our practical solutions. These solutions encompass methods and tools on the one hand and organizational and personal prerequisites on the other hand. All these measures facilitate enhanced design quality and efficient development of excellent software products with a positive user experience.
Ulf Schubert, Martin Groß, Stefanie Pötzsch
Start the Game: Increasing User Experience of Enterprise Systems Following a Gamification Mechanism
Abstract
“Hi dear, how was your day?” In the rarest of cases the responded would answer: “I had so much fun when entering the customer data into our Enterprise Systems.” However, the usage of Enterprise Systems is nowadays for many employees a key element of their working activities. Therefore, their motivation to use these systems consistently is essential for organizations to ensure transparency and process accuracy. While today most software products have a high usability, they lack in positive user experiences such as fun. One trend having the potential to solve this issue is Gamification. Using mechanisms of traditional games such as achievements or rankings is successfully implemented in private applications such as social networks (e.g. Facebook) or online traveling portals (e.g. tripadvisor). These mechanisms motivate individuals to perform certain activities they would otherwise not do. Gabe Zichermann – a visionary of Gamification – explained this phenomenon as following: Games are the only force in the known universe that can get people to take actions against their self-interest, in a predictable way, without using force. The principle of Gamification and its potential in organizations is presented in this book chapter.
Maik Schacht, Silvia Schacht
Introduction of Software Product Management at Wincor Nixdorf: Challenges and Lessons Learned
Abstract
The importance of product management in the software industry is widely recognized and empirically validated. Despite its importance, the maturity level of software product management in companies is low, many companies struggle with the challenge of introducing product management. This paper describes a real-world industry experience report of a product management introduction project in a banking and retail IT Solutions Company. We illustrate the initial situation before the product management introduction project, the approach that has been pursued within the project, the challenges of the first year and the experiences that have been made.
Christian Schloegel
Intertwining Lean and Design Thinking: Software Product Development from Empathy to Shipment
Abstract
A few years back, everybody in the industry seemed to be talking about how “Lean Thinking” can improve software development. Best practices emerged, books were written and Lean Thinking, associated with agile process frameworks became somewhat of a standard work culture in software development. Now that many people are actually practicing lean and agile development, they have started to wonder about something called “Design Thinking”. When we coach development teams in a large software company, we’re frequently being asked whether Design Thinking is the next big thing substituting lean software development. After having guided several teams through successful projects, our verdict is: Design Thinking is not Lean’s heir; in fact the two schools can be intertwined in many ways and complement each other very well. As we will elaborate in this case study, they share some integral core values and goals, and can therefore be applied in the same project without corrupting each other. As a proof of concept, we combined and utilized the underlying set of methods in order to explore a yet relatively unknown and unusual domain for SAP business applications: Software for professional sailors and their coaches that helps them to optimize their training experience and competitive performance.
Tobias Hildenbrand, Johannes Meyer
The Relationship Between Scrum and Release Planning Activities: An Exploratory Case Study
Abstract
In modern product software development settings, it becomes increasingly important to deal with rapid changes in scope, large numbers of users, and regular releases. These circumstances are ideal for an agile development method such as Scrum to prove its value. However, the implications that Scrum has on software product management (SPM) processes have not been investigated in detail. In this paper, we provide more insight into the link between release planning processes and Scrum, by performing a case study at a large Dutch social network provider. The results show an evolutionary approach to the implementation of Scrum, and the relation between several Scrum concepts and SPM capabilities. The findings presented in this paper contribute to more insight into the link between Scrum and SPM and can be of help to product software organizations that employ the Scrum development method.
Michail Theuns, Kevin Vlaanderen, Sjaak Brinkkemper
Lessons Learned in the Development of a CRM SaaS Solution
Abstract
Software as a Service (SaaS) solutions have gained a significant momentum in the past few years. They promise to vastly simplify the long way from identifying the need for a new software system until its successful operation at a customer. Essentially, SaaS solutions have to face two potentially conflicting requirements: On one hand, customers expect that the software they use in the cloud can be customized smoothly to solve their specific business needs and requirements. On the other hand, they need to exploit the economy of scale principle by employing an architecture that handles all customers uniformly. This article examines these and a number of other requirements to SaaS systems and will shed some light on architectural concepts addressing these requirements. It illustrates some of the concepts with examples from a Java based SaaS solution for customer relationship management (CRM) and provides some lessons learned gained during the development and the first few years of offering the product on the market.
Markus Bauer
Backmatter
Metadata
Title
Software for People
Editors
Alexander Maedche
Achim Botzenhardt
Ludwig Neer
Copyright Year
2012
Publisher
Springer Berlin Heidelberg
Electronic ISBN
978-3-642-31371-4
Print ISBN
978-3-642-31370-7
DOI
https://doi.org/10.1007/978-3-642-31371-4

Premium Partner

    Image Credits