Agile in 3D: Agility in the Animation Studio

Filho, Avelino Ferreira Gomes; Alencar, Danilo; Toledo, Rodrigo

doi:10.1007/978-3-319-73673-0_5

Cited by 1 publication

(4 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Notable ones can be listed as follows: simultaneously used number and size-based WIP, iterative movement of the items on the flow, work/hypothesis/experiment/release-based iterations, calendar-based regular or on-demand ceremonies, daily planning, team formations that break the <standard= cross and self-organizing team structures including floating teams, subgroups/roles and supervisory authority, same/similar-size work items, and product owner teams. [28], [29], [32], [33], [34], [39]-Case1, [40], [41], [49], [56] Daily 9 -[26], [28], [33], [38], [41], [44], [49], [51], [52] Scrum Team…”

Section: Collective Understandingmentioning

confidence: 99%

“…6 -[28], [32], [34], [44], [49], [56] User Story 5 -[26], [28], [32], [38], [51] Definition of Done 5 -[28], [34], [38], [44], [51] Sizing (T-Shirt size, effortbased, planning poker etc. )…”

Section: Collective Understandingmentioning

confidence: 99%

“…16 -[26], [28], [29], [32], [33], [34], [38], [39]-Case1, [39]-Case2, [40], [41], [44], [49], [51], [52], [56] Work in progress (WIP)…”

Section: Collective Understandingmentioning

confidence: 99%

“…Some teams regard Scrum as difficult to accept with its revolutionary transformation change proposition [45], <aggressive=, <materialized= and <rigid= structure [42], [46]. [28], [29], [32], [33], [34], [40], [44], [45], [55], [56], [57] Quality decrease Telco, Content, Web, Auto, Soft 5- [29], [38], [39], [40], [46] Unsuitable for maintenance System, Maintenance, Soft 4- [34], [44], [46], [55] Estimation is timeconsuming, non-sensing, or causing delays Web, Content, Soft 3- [38], [40], [46] Scrum ceremonies cost Mob, Finance…”

Section: -[40]mentioning

confidence: 99%

See 3 more Smart Citations

Scrum, Kanban or a Mix of Both? A Systematic Literature Review

Ozkan¹,

Bal²,

Erdogan³

et al. 2022

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

4Among the Agile methods, Scrum and Kanban are widely used in software development and they are considered the two most effective ones influencing the direct results of projects. Despite the importance of knowing their relative strengths and advantages and integrating them to achieve better results than individual use, none of the secondary studies provide extensive knowledge on the topic. In this paper, we performed a Systematic Literature Review (SLR) study to investigate the characteristics of the empirical studies which involve Scrum and Kanban by comparing or integrating them. Our final set includes 38 studies posing primary information on the advantages of each method over another one, the properties including artifacts, roles, and events from Scrum and Kanban in combining them in a hybrid way, and the properties of transitions from one to another such as transition directions (Scrum to Kanban, Kanban to Scrum or Scrum/Kanban to Hybrid), transition years, and transition reasons. The outputs can be interesting for both industry and researchers. For example, nearly all of the transitioning organizations are moving from Scrum to Kanban or to hybrid method. Among the reasons for the transitions, the problems experienced with Scrum are remarkable. In comparison, Kanban stands out clearly in a positive way. Almost all of the teams combining both use flow instead of a sprint.

show abstract