Figure 1 - uploaded by Eduardo Miranda
Content may be subject to copyright.
Source publication
Time boxing is a management technique which prioritizes schedule over deliverables but time boxes which are merely a self, or an outside, imposed target without agreed partial outcomes and justified certainty are at best, an expression of good will on the part of the team. This essay proposes the use of a modified set of Moscow rules which accompli...
Contexts in source publication
Context 1
... is clear that by scheduling features at the safe level, the most work we can accommodate within the time box boundaries is that depicted by the patterned area in Figure 1.b. So for the "must have" category the 2 More sophisticated approaches such as Statistically Planned Incremental Deliveries -SPID [1] will require three points estimates and the specification of an underlying distribution 3 As I did in the redefining of the MOSCOW categories in this article I am avoiding the temptation of calling these estimates the 50% and the 90% probability estimates to prevent giving a false sense of mathematical exactness, which will require the making of additional assumptions or an analysis that might not be justified by the practical impact of the added accuracy and precision. 4 If a single project had to ensure against all possible risks and uncertainty, its price would be prohibitive [5] customer must select, from among all requirements, those which are more important for him until exhausting the number of development hours available while scheduling them at the safe effort level. This is the constraint missing in other prioritization methods and the key to provide a high level of confidence, in spite of the uncertainty of the estimates and the speed of execution, in the delivery of features in this ...
Context 2
... the "must have" requirements have been selected, we will re- schedule them using their normal estimates, see figure 1.c, and reserve the difference between the two effort levels as a buffer to protect their delivery. We will repeat the process for the "should have" and "could have" requirements using the size of the buffer protecting the previous category as the initial budget for the current one, see figure 1.d. The requirements that could not be accommodated in any category at their safe level become the "won't ...
Context 3
... the "must have" requirements have been selected, we will re- schedule them using their normal estimates, see figure 1.c, and reserve the difference between the two effort levels as a buffer to protect their delivery. We will repeat the process for the "should have" and "could have" requirements using the size of the buffer protecting the previous category as the initial budget for the current one, see figure 1.d. The requirements that could not be accommodated in any category at their safe level become the "won't ...
Context 4
... we wanted to be reassured of being able to deliver all features under most circumstances we would need to plan for the worst case, which means scheduling all deliverables using their safe estimate. This, more likely than not, will exceed the boundaries of the time box 4 . See Figure ...
Similar publications
Coordination is an important but challenging success factor in large-scale software development. Large-scale is particularly demanding because it involves several teams, and therefore we chose to study coordination between teams. Our aim of this case study was to investigate inter-team coordination mechanisms. By using an established framework from...
Software effort estimation process in any software project is not only essential, but also a very critical component. The success or failure of projects depends heavily on the accuracy of effort and schedule estimations, among other things. The emergence of agile methods in the software development field has presented many opportunities and challen...
In modern software development processes, software effort estimation plays a crucial role. The success or failure of projects depends greatly on the accuracy of effort estimation and schedule results. Many studies focused on proposing novel models to enhance the accuracy of predicted results; however, the question of accurate estimation of effort h...
In modern software development processes, software effort estimation plays a crucial role. The success or failure of projects depends greatly on the accuracy of effort estimation and schedule results. Many studies focused on proposing novel models to enhance the accuracy of predicted results; however, the question of accurate estimation of effort h...
Citations
... Dużego doświadczenia Rys. 4 wymaga właściwe dobranie zakresów projektów w stosunku do nakładu pracy studenta. Na podstawie analizy wyników oraz konsultacji z uczestnikami projektów w trakcie ostatnich trzech edycji przedmiotu projekt grupowy wprowadzono podział zakładanych wyników realizacji projektów jako opcje właściwe dla modelu priorytetyzacji MoSCoW [76]. Takie podejście usprawnia prace projektowe. ...
W pracy opisane zostały doświadczenia związane z realizacją zespołowych projektów studenckich w odniesieniu do formy ich przygotowania, organizacji oraz realizacji z partnerami z branży IT. Ponadto przedstawione zostały elementy związane z pracą w zespole w powiązaniu z wybranymi elementami procesu wytwarzania oprogramowania. Omówiono proces kształtowania umiejętności pracy w zespole, który został opracowany na bazie wieloletnich doświadczeń.
... On the other hand, it is necessary to prioritize what is essential for the operation of the product for the development [16,17]. The prioritization technique that has been used as a reference to prioritizing the requirements is MoSCoW [27,28]. ...
... The MoSCoW method [28] is a prioritization technique [17] used in management, business analysis, project management, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement -also known as MoSCoW prioritization or MoSCoW analysis [27]. The prioritization categories are typically understood as: must have, should have, could have, and won't have [28]. ...
... The MoSCoW method [28] is a prioritization technique [17] used in management, business analysis, project management, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement -also known as MoSCoW prioritization or MoSCoW analysis [27]. The prioritization categories are typically understood as: must have, should have, could have, and won't have [28]. ...
There are some significant tasks in the first stage of a project in order to achieve success when taking out a new product, a service or release a software. It is essential to know what is in the market and what the potential customers want. Therefore, during the project, we performed a market analysis regarding all the products related with IoT and we had interviews with all the involved actors in all the domains, such as developers, integrators, operators, domain users, clients, etc. Furthermore, from the previous information we define the requirements in order to determine how the system should work and what it should do. This chapter presents the process and the results of these three activities developed in the first stage of the INTER-IoT project: market analysis, stakeholders analysis, and requirements analysis. This task was done for the five different products defined in the project: INTER-LAYER, INTER-FW, INTER-METH, INTER-LogP, and INTER-Health. These tasks have been made using the VOLERE methodology, which is an excellent methodology to extract conclusions and provide results following a systematic approach.
... A definição de requisito, segundo a norma IEEE Std 1233-1996, é vista como "uma condição ou capacidade necessária para um utilizador resolver um problema ou atingir um objetivo" [95]. Nas secções seguintes serão apresentados os vários requisitos, distinguindo-os consoante a prioridade necessária, utilizando para isso a metodologia MoSCoW [133], resultando a priorização em quatro categorias: ...
With the growth of social media and the spread of the Internet, the user's opinion become accessible in public forums. It became then possible to analyse and extract knowledge based on the textual data published by users, through the application of Natural Language Processing and Text Mining techniques. In this dissertation, these techniques are used to, based on comments posted by users on YouTube, extract information about Usability, User Experience (UX), and Perceived Health Impacts related to Quality of Life (H-QoL). This analysis focus on videos about the Just Dance series, one of the most popular interactive dance video games.Just Dance belongs in a category of games whose purpose goes beyond entertainment - serious games - among which there is a specific type of games, exergames, which aim is to promote physical activity. Despite their positive influence on the health of their users, these often stop playing after a short period of time, leading to the loss of benefits in the medium and long term. It is in this context that the need to better understand the experience and opinions of players arises, especially how they feel and how they like to interact, so that the knowledge generated can be used to redesign games, so that these can increasingly address the preferences of end-users.It is with this purpose, that in a serious game it is necessary to assure not only the fundamental characteristics of the functioning system, but also to provide the best possible experience and, at the same time, to understand if these positively impact players' lives. In this way, this dissertation analyses three dimensions, observing, besides Usability and UX aspects, also H-QoL, in the corpus extrated for this dissertaion.To meet the objectives of this dissertation, a tool was developed that extracts information from user comments on YouTube, a social media network that despite being one of the most popular, still has been little explored as a source for opinion mining. To extract information about Usability, UX and H-QoL, a pre-established vocabulary was used with an approach based on the lexicon of the English idiom and its semantic relations. In this way, the presence of 38 concepts (five of Usability, 18 of UX, and 15 of H-QoL) was annotated, and the sentiment of each comment was also analysed. Given the lack of a vocabulary that allowed for the analysis of the dimension related to H-QoL, the concepts identified in the World Health Organization's WHOQOL-100 questionnaire were validated for user opinion mining purposes with ten specialists in the Health and Quality of Life domains.The results of the information extration are displayed in a public dashboard that allows visitors to explore and analyse the existing data. Until the moment of this dissertation, 543 405 comments were collected from 32 158 videos, in which about 52% contain information related to the three dimensions. The performance of this annotation process, as measured through human validation with eight collaborators, obtained an general efficacy of 85%.
... Development of the program took place using the MoSCoW method (Miranda, 2011), starting with the determination of the minimal requirements for a working and accessible game (so-called 'Must haves'). In addition, 'Should haves' (i.e. ...
... Continuing, the formalization of rules will be based on the MoSCoW method [13], which is a prioritization technique used in management, business analysis, project management and software development. This method aims to achieve a typical comprehension among stakeholders about the importance they set at a process. ...
Lean theory, principles and tools, are intended to highlight the value within the company and eliminate waste entirely. Despite the large amount of literature work on lean, there is a lack of in-depth analysis for collection and categorization of specific lean rules for the manufacturing industry. Therefore, the present work proposes a classification, formalization and identification of lean rules, in order to create a comprehensive and applicable library of lean rules, after the investigation of academic literature and a mould-making industry. Finally, the “drawer” idea is introduced aiming to motivate employees of different hierarchical levels in the lean rules development.
... Simplicity is often mentioned as one of its biggest advantages. There also been a proposal of modifying MoSCoW rules to add time boxes and buffering (Miranda 2011). ...
In contemporary economy one observes numerous changes in the sphere of functioning of the companies. These trends include inter alia globalization combined with occurrence of global corporations and global products, rapid technical and technological growth, cooperative ventures between the companies (irrespective of their forms), occurrence of the new management concepts and others. Under these new circumstances, effective management becomes a matter of a key importance, which may reduce the risk which is inherently associated with the company’s activity. In other words, it is crucial to the success of the every company. Therefore, managers have to have knowledge about factors which are crucial in the management process.
Given these facts, the mission of this monograph is a complex presentation of the most important topics associated with the management of modern companies. The monograph consists of both theoretical and practical chapters which are written by the scholars from several Central European countries. In other words, the perspective of different countries, as well as different scientific disciplines has been presented in the book.
... ". There are papers that are trying to extend MoSCoW functionalityfor example a proposal of modifying MoSCow rules to add time boxes and buffering (Miranda, 2011). ...
In this paper authors discuss the problem of requirements prioritization as a part of requirements elicitation, addressing the problem in agile software development methodologies. Related work in the field is enumerated, together with most important concepts and their strengths and weaknesses; Kano model of customer satisfaction is discussed as non-complete solution to the problem; then the proposed approach, which modifies the process , is researched and explained in order to present actual analysis of presented case study. Authors' approach assumes that MoSCoW rules could be useful for requirements elicitation process, this approach also extends a couple functionalities further. Conclusions and observations for future work are presented as well.
The paper documents some of the results of the research program Smart Yard: Industry 4.0 Production Process aimed at reducing inefficiencies in construction site procedures by developing new management methods supported by digitisation processes that can memorise and monitor computational data and guide them towards specific purposes of production processes optimisation. In particular, the aim of the study is to propose evolved, highly efficient and innovative organisational and information management models that enable more reliable control of processes in the construction sector, mitigating unavoidable uncertainties while pursuing a more rational use of resources. The products developed to support the programme include two newly designed pieces of equipment with advanced functions, which can be configured as examples of site management systems such as a “smart factory” in the logic of Industry 4.0, illustrated below. One is a high-performance charging system for power banks to be used with portable power tools, while the other concerns a work standing desk that employs wireless communication protocols to dialogue with other devices at the construction site
In the midst of the 21st-century digital revolution, we find ourselves navigating a complex landscape where our analog instincts clash with our digital dependencies. Our smartphones, compact marvels of technology, house the entirety of our daily existence, from groceries to fashion and medicine. Yet, amidst this convenience, fundamental questions about data safety, security controls, and data ownership linger ominously in our minds. This chapter delves into the vital trifecta of privacy, security, and data ownership in our increasingly digitized world. In an era of ever-evolving technology, the ordinary user constantly frets about the sanctity of their data. While technology has undoubtedly bestowed countless benefits upon humanity, it also bears a dark side, epitomized by the surge in digital frauds and scams. Such concerns propel individuals to ponder deeply: Is my data truly private? and Who ultimately lays claim to, or safeguards, my data? This exploration ventures into the realms of artificial intelligence, virtual reality, the metaverse, online payments, and virtual classrooms.
This paper describes the Milestone Driven Agile Execution (MDAX) framework. MDAX is hybrid development approach, in which the just-in-time planning of tasks and the empirical control of the agile methods are retained, but the prioritization of the backlog is done according to a milestone plan that drives the execution of the project. Selecting work items from the backlog according to a plan, instead of the weekly or biweekly, sometimes haphazard, concerns of the team or the product owner, adds visibility, predictability, and structure to the work of the team while preserving the adaptive advantages of current agile methods.
MDAX takes a collaborative and visual approach to planning which promotes participation, communication and buy-in into the plan. It uses large canvasses and the direct manipulation of planning artifacts to generate engagement .