|
||||
T1 T2
DETAILS
T1 There are many methods supporting software developers in their daily work. They range from heavyweight waterfall-oriented to lightweight agile-oriented methods. Although many of them are good when being used for developing the right product in the right context, they still cannot provide full support to all kinds of software development efforts. Reasons are many and they are mainly project and product specific. Neither can the existing methods be compared due to varying contents of their method ingredients and the vocabulary used. In search of finding optimal ways of developing software, companies either improve their methods or adapt the new ones. This may be a very risky undertaking that may not always bring the desired benefits. Strong belief in the goodness of the method improvements or of the new methods may imply pitfalls in form of huge costs and lowered product and process quality. To remedy the problem of strong method diversity and incompleteness, a new meta-method has been developed by the SEMAT community [1, 3]. The meta-method is called Essence – Kernel and Language for Software Engineering Methods and it has just been accepted as an OMG standard. Essence is an innovative approach to managing software engineering endeavors [2]. As a meta-model, it may be used for supporting the currently existing software development methods. Essence consists of (1) the kernel of elements that are universal and essential for all kinds of software development efforts and (2) the language to be used for composing practices and methods. This tutorial demonstrates how the Essence Kernel and its concepts may be used in practice. It first introduces the Kernel and then continues with the demonstration of how to use the Kernel in practice. Using a close to real-world development scenario and the Essence game cards, the tutees will gain understanding of how the Essence Kernel can support Scrum and the team in identifying project status and health. REFERENCES
T2 The tutorial is about what is innovation, and how to involve users in innovation processes? Every year, many products and services are developed, but ultimately fails. A user-centric approach may reduce the risk of failures. The tutorial will discuss innovation, why users should be involved, and techniques to facilitate user involvement. User involvement should happen in all stages of the product or service lifecycle. User-centric thinking will be explained through practical examples from public sector innovation projects combined with experiences from the NET-EUCEN thematic network. |
||||
Copyright (c) 2006-2014, IARIA