Digite
MAY 15, 2018
Inspired by Steve Porter’s efforts to bring process practitioners closer together and educate Scrum practitioners, I’m writing a shadow series of posts that will follow the Kanban and Scrum – Stronger Together series and continue my own efforts to clear up misconceptions between practitioners of these methods.
Scrum.org
AUGUST 25, 2022
This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. Many studies have shown that stressed developers make more mistakes (Furuyama, Arai & Lio, 1996, Sonnentag et. References.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
NOVEMBER 24, 2021
Van Waardenburg & Van Vliet (2013) offer a case study in a large organization and conclude that “The Project Manager focuses on the ’how’ of a project, the Product Owner focuses on the ’what’”. Communicator : The transfer of knowledge between different sites, as well as from and to the team. Insight #3: Product Discovery Is Missing?
Scrum.org
MARCH 31, 2020
Despite the rapidness of the change, moving to remote worked surprisingly well for many teams, because they were used to some degree of remote work before. Especially development teams and technology firms in general have many years of experience with allowing their workforce to do their jobs from wherever and whenever they like.
ProjectManager.com
MARCH 4, 2022
The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. For this purpose it defines three roles, a scrum master, a product owner and a development team, made up of several team members.
Digite
JUNE 13, 2018
Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development. Make Process Policies Explicit.
Gunther Verheyen
FEBRUARY 3, 2018
I took the opportunity to revisit my original text (dating from 2013). Questo evento serve al Development Team per condividere i progressi giornalieri, pianificare il lavoro delle 24 ore successive e per aggiornare lo Sprint Backlog di conseguenza. It resulted in small revisions and an update to my Scrum Glossary. Scrum (sost.
Expert insights. Personalized for you.
93 
Let's personalize your content