Videos on Scrum and Agile Project Management
The board game Othello has the slogan: “A minute to learn, a lifetime to master.” This applies really well to a team that’s learning Scrum. The basic practices and mechanics of Scrum are straightforward, and not difficult to adopt.
Knowing the basics of Scrum is essential for any team member, but out in the trenches, a good ScrumMaster must be ready to identify and deal with Agile Antipatterns quickly to help his team and organization move forward.
The rhythm of Agile software development is to always be working on the next known, small batch of work. Is there a place for software architecture in this style of development? Some people think that software architecture should simply emerge and doesn’t require ongoing attention. But it isn’t always prudent to let the software architecture emerge at the speed of the next iteration.
Scrum is a lightweight framework for building complex software in complex environments and Prince2 is a framework for managing projects. Contrary to popular belief, the two work well together with the degree of governance large organisations require.
The prioritized product backlog is core to being Agile. A well prioritized backlog allows us to satisfy the customer through early and continuous delivery of valuable software at then end of each sprint in Scrum. Lean and Kanban may call it something else, but there too, prioritized work is key.
Soft factors include beliefs, character and attitude of people as well as the way we communicate. This presentation addresses for example: Why are we acting in a certain way? Who must change: Me or the other person? I “want” is better than I “must”. How to find out the true reason behind somebody’s behaviour? How can we win people instead of forcing them?
What is the key to high productivity via Scrum? According to Alex Brown, Chief Operating Officer at Scrum Inc., it all comes down to the retrospective and the “happiness metric.”
Scrum Expert Copyright © 2009-2024 Martinig & Associates