Full-text resources of CEJSH and other databases are now available in the new Library of Science.
Visit https://bibliotekanauki.pl

Results found: 9

first rewind previous Page / 1 next fast forward last

Search results

Search:
in the keywords:  Scrum
help Sort By:

help Limit search:
first rewind previous Page / 1 next fast forward last
EN
The paper first presents basic information about the Scrum method. Then it summarizes the state of art in the domain of Scrum implementation, especially as far as the critical factors of its success are concerned. On the basis of literature survey a new model classifying Scrum implementation critical factors is proposed. The model divides Scrum implementation critical factors into five categories: Project Team factors, Psychological and cultural factors, Process and Method, Environment and Technology. The model is then developed and verified using the case study method. The research was carried out in a French IT company by means of a participating observation. The company was implementing Scrum, which ended up as a success. A journal of the Scrum implementation was conducted, presenting the experiences of the Scrum Team, their opinions and changes in the Scrum method which were introduced. On its basis critical factors, crucial for the success of Scrum implementation, classified according to the above mentioned model, were identified, completing those which had been found in the literature.
EN
The article focuses on the issues of project control in Scrum methodology representing agile approach, in which control is based specifically on the daily meetings. Based on own experience and discussions with members of the Scrum development teams, in this study 19 core problems associated with daily meetings are identified and possible solutions are discussed. Then an environmental study is conducted to verify the classification of the problems and to determine the practical approach to daily meetings in IT companies. On the basis of the collected results, a brief assessment of the quality of daily meetings is provided, which depends on the Scrum team development stage.
3
89%
PL
W artykule został dokonany przegląd znanych w literaturze modeli dojrzałości oraz zaproponowano model dla podejścia Scrum. Model ten pozwoli każdej organizacji ocenić jakościowo i ilościowo stopień dojrzałości wdrożenia podejścia Scrum w poszczególnych projektach i w organizacji. Jest on oparty na ankiecie, którą wypełniają osoby zaangażowane w różnych rolach w realizację projektów informatycznych wykorzystujących podejście Scrum.
EN
In the paper, a survey of maturity models known in the literature is conducted. A new model for the Scrum approach is proposed. The model will allow each organisation to evaluate quantitatively and qualitatively the degree of maturity of the Scrum implementation in individual projects and in the whole organisation. The model is based on a questionnaire filled in by persons playing different roles in IT projects using the Scrum approach.
EN
IT companies are constantly looking for effective methods of software development. Typically, these approaches are tailored to the type of software development work. The most popular are the agile, lean and proactive (classic) approaches. The study will assess the methodology that synergistically combines the agile and lean approaches. Representatives of these approaches are Scrum and Kanban. As a result of this assessment, optimal solutions for software development teams will be proposed. A case study of using a solution combining agile and lean approaches will be presented.
PL
W firmach informatycznych cały czas poszukiwane są efektywne metody rozwoju oprogramowania. Zwykle te podejścia dostosowywane są do rodzaju prac związanych z rozwojem oprogramowania. Do najbardziej popularnych należą podejście zwinne (agile), szczupłe (lean) i proaktywne (klasyczne). W opracowaniu poddana zostanie ocenie metodyka łącząca w sposób synergetyczny podejście zwinne (agile) i podejście szczupłe (lean). Reprezentantami tych podejść są Scrum i Kanban. W wyniku tej oceny zostaną zaproponowane optymalne rozwiązania dla zespołów rozwijających oprogramowanie. Przedstawiony zostanie przykład studialny (case study) użycia rozwiązania łączącego podejście zwinne i szczupłe.
PL
W artykule zostały przedstawione wyniki badań dotyczące skuteczności wdrażania zwinnych metodyk w ramach realizowanych projektów przez wybrane grupy studentów technicznych. Została opisana zastosowana gra symulacyjna, która pozwoliła na praktyczne zapoznanie się z zasadami podejścia Scrum. Przedstawiono również propozycję praktycznej adaptacji podejścia zwinnego do realiów projektów studenckich z uwzględnieniem specyfiki i ograniczeń czasowych.
EN
The paper presents the results of research on effectiveness of agile methods implementation within projects carried out by selected IT student groups. Simulation game was applied for groups under research, which helped subjects to experience Scrum rules in practice. We present the results of the game and the proposal for practical adaptation of agile approach into student projects taking into consideration their specifics and time constraints.
6
Publication available in full text mode
Content available

Agile crisis management

89%
PL
Artykuł dotyczy zarządzania kryzysowego. Autorzy zaproponowali nowe podejście oparte na zwinnych metodach zarządzania projektami. W pracy zaprezentowano kolejno: kryzys i zarządzanie nim (przegląd literatury), charakterystykę projektów informatycznych, zwinne zarządzanie projektami, analizę porównawczą zwinnego podejścia i zarządzania kryzysowego, propozycję nowego pomysłu – zwinne zarządzanie kryzysowe. We wnioskach podkreślono potrzebę kontynuacji prowadzonych badań empirycznych.
EN
The article deals with crisis management. A new approach based on the agile methodologies of project management is proposed. The paper presents consecutively: crisis and its management (literature overview), characterisation of IT projects, agile project management, comparative analysis of agile approach and crisis management, proposal of a new idea – agile crisis management and conclusions. The conclusions emphasise the importance of following up with necessary empirical investigations.
EN
A proper estimation of time in user stories is a crucial task for both the IT team as well as for the customer, especially in agile projects. Although agile practices offer a lot of flexibility and promote a culture of continuous change, there are always clearly de need timeboxed periods where an IT company has to commit to delivering working soft-ware. Estimating time of user story implementation provides clarity and the opportunity to control the project by the management, yet at the same time, it can increase pressure on software developers. Thus, incorrectly estimated user stories may lead to quality problems including system malfunction, technical debt, and general user experience issues. The paper describes user story characteristics, reasons of user story estimation inaccuracy as well as a model of their potential impact on post-release defects in large IT software ventures, all derived from the conducted interview with practitioners in Capgemini software development company.
EN
The increasing use of agile methods for software development creates the need for these methods to become part of the education of future computer and information science engineers. On the other hand, teaching these methods gives us an opportunity to verify individual agile concepts and their effectiveness. For that reason, project work is an appropriate and frequently used form of teaching that enables students to get acquainted with agile methods and, at the same time, provides case studies for evaluating individual agile concepts. We describe our approach to teaching the Scrum agile method, within the software technology course, in cooperation with a software development company. Students were taught through work on a real project for which a list of requirements was submitted by the company. A co-worker of this company participated throughout the teaching period playing the role of customer's representative. During their work, students consistently used the Scrum method and at the end of each iteration they evaluated their experience by means of a questionnaire. In the article, the Scrum method is presented first, then a description of work on the project is given and finally the results of the survey are described.
PL
Artykuł dotyczy zarządzania mediami, dlatego odpowiednio zaprezentowano próbę możliwego podejścia opartego na zwinnych metodologiach zarządzania projektami. Artykuł przedstawia kolejno media i zarządzanie nimi (przegląd literatury), charakterystykę projektów medialnych, zwinne zarządzanie projektami, analizę zwinnego podejścia i zarządzania mediami wraz z propozycją nowego pomysłu, jakim jest zwinne zarządzanie mediami (Agile Media Management) oraz wnioski. Poniższe wyniki podkreślają istotną potrzebę przyjrzenia się tej idei w ramach ważnego badania empirycznego oraz dalszego kierunku badań.
EN
An attempt has been made to propose a new approach to media management. Its starting point is the similarity of the main media and its management features, with some elements of agile methodologies. The approach mentioned in the article would eradicate all of the documentation, and make media management as genuine and effective as possible. The proposal within the article is not yet created as a methodology because the aim of this publication was to show the current possibilities in creating such foundations for the future possible methodology implemented inside the media management scheme. The invitation of all specialists in the field of project management, Agile, and traditional project management approaches would be greatly appreciated. The need of an in-depth analysis of how an agile approach can be applied in such a relatively young industry is still plausible. In sum, there are numerous agile tools that can be adopted in media management. The first proposal of media management has been already published by independent researchers, yet this work should be done primarily in the form of more detailfocused and thorough analysis.
first rewind previous Page / 1 next fast forward last
JavaScript is turned off in your web browser. Turn it on to take full advantage of this site, then refresh the page.