Content tagged with: people
During the presentation I’d like to give you opportunity to look at various countries and organizations cultures to discuss challenges in introducing and using agile there. We’ll learn some nice lifehacking tricks how use the differences in most efficient way.
Adopting an Agile approach in a software development organization requires more than just sending some people to a Certified ScrumMaster (CSM) course. In this article, John Hill provides six recommendations for an enterprise Scrum transformation.
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?
How do effective Agile and Scrum leaders act? Agile advice often mentions abstract concepts, like allow the team to self-organise, without illustrating what a leader should do if this doesn’t happen or things go wrong.
The patterns and anti-patterns of human system design sound familiar. This presentation discusses a few of them, including: Good/Bad UX, Enlightening/Confounding Data, Robust/Weak Architecture.
Linda Rising shares influence strategies that you can use to more effectively convince others to see things your way. You’ve tried and tried to convince people of your position. You’ve laid out your logical arguments on impressive PowerPoint slides—but you are still not able to sway them. Cognitive scientists understand that the approach you are taking is rarely successful. Often you must speak to others’ subconscious motivators rather than their rational, analytic side.
Martin Alaimo thinks that personal issues are rarely discussed in Scrum retrospectives. In this article, he discusses how he includes in retrospectives a special section to address personal issues. He explains how he uses retrospectives to build Scrum between the Scrum team members.
In Agile and Scrum, we spend a lot of time talking about how to better manage software development teams using processes, methods, prescriptions and other rules of thumb. We spend very little time talking about the largest and most important ingredient of any agile team: the team and people themselves
Self-organizing Scrum and agile teams need to determine how best to manage the flow of their work to get the job done each iteration. Flexible and high-performing agile development teams are composed of members with T-shaped skills and a Musketeer attitude that enable them to swarm to success.
If Scrum provides the project management framework used in a majority of Agile projects, eXtreme Programming (XP) is the main source of technical practices for Agile software development. This book written by Alan Shalloway, Scott Bain, Ken Pugh and Amir Kolsky is focused on these technical aspects. The first part deal with the coding and testing activities and the second part discusses how to handle the software design activity with an Agile perspective.