Topic
User story
About: User story is a research topic. Over the lifetime, 1078 publications have been published within this topic receiving 23717 citations.
Papers published on a yearly basis
Papers
More filters
••
19 Oct 2007TL;DR: If the user is given advice, the number of queries she needs to try before finding the product of highest utility is greatly reduced and an advisor that confines its advice to queries that the user model predicts are likely to be tried next will give shorter advice than one whose advice is unconstrained by the user models.
Abstract: Consider a conversational product recommender system in which a user repeatedly edits and resubmits a query until she finds a product that she wants. We show how an advisor can: observe the user's actions; infer constraints on the user's utility function and add them to a user model; use the constraints to deduce which queries the user is likely to try next; and advise the user to avoid those that are unsatisfiable. We call this information recommendation. We give a detailed formulation of information recommendation for the case of products that are described by a set of Boolean features. Our experimental results show that if the user is given advice, the number of queries she needs to try before finding the product of highest utility is greatly reduced. We also show that an advisor that confines its advice to queries that the user model predicts are likely to be tried next will give shorter advice than one whose advice is unconstrained by the user model.
29 citations
••
05 Apr 2004TL;DR: In this paper, an empirical case where a project using Extreme Programming (XP) based approach was assessed using the CMMI framework, the results provided empirical evidence pointing out that it is possible to achieve maturity level 2 with approach based on XP.
Abstract: The relationship between agile methods and Software Engineering Institute’s CMM approach is often debated. Some authors argue that the approaches are compatible, while others have criticized the application of agile methods from the CMM perspective. Only few CMM based assessments have been performed on projects using agile approaches. This paper explores an empirical case where a project using Extreme Programming (XP) based approach was assessed using the CMMI framework. The results provide empirical evidence pointing out that it is possible to achieve maturity level 2 with approach based on XP. Yet, the results confirm that XP, as it is defined, is not sufficient. This study demonstrates that it is possible to use the CMMI for assessing and improving agile processes. However, the analysis reveals that assessing an agile organization requires more interpretations than normally would be the case. It is further concluded that the CMMI model does not always support interpretations in an agile context.
29 citations
••
01 Jan 2012TL;DR: The 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 and can therefore be applied in the same project without corrupting each other.
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.
29 citations
••
25 May 2003TL;DR: The authors used an interpretative in-depth case study to explore a successful XP project and obtained multiple perspectives on the implementation of the customer role, and this paper includes excerpts from interviews with the customer and other development team members.
Abstract: One of the pivotal roles in XP is the customer, but little guidance is provided in the literature on the practicalities of succeeding in this role. We used an interpretative in-depth case study to explore a successful XP project. We obtained multiple perspectives on the implementation of the customer role, and this paper includes excerpts from interviews with the customer and other development team members. We found that the interviewees provided a consistent picture of the XP customer role and they agreed that the XP customer role, especially for larger organisations, is very demanding. It requires preparation, skills, attention to detail, and the ability to make critical decisions.
29 citations