recentpopularlog in

scrum

« earlier   
Developers Should Abandon Agile
learn to work this way:

Produce running, tested, working, integrated software every two weeks, every week. Build your skills until you can create a new fully operational version every day, twice a day, multiple times a day.
Keep the design of that software clean. As it grows, the design will tend to become complex and crufty. Resist and reverse this tendency consciously, refactoring in tiny continuous steps, all the time, so that your rate of progress is as steady and consistent as possible.
Use the current increment of software as the foundation for all your conversations with your product leadership and management. Speak in terms of what’s ready to go, and in terms of what they’d like you to do next.

This is the development team’s best hope for a reasonable life. By keeping the software always ready to go, we can hit any deadline with the best possible result. “Is today the deadline? Here’s what we’ve got, it’s ready to ship.”
programming  agile  scrum 
5 days ago by photoangell
Twitter
Breaking News:  I will be giving a CSM course in Timisoara in July.  Details and registration at
scrum  from twitter_favs
6 days ago by ralfhh
Twitter
Nächsten Monat, vom 11.-13. Juli, präsentiert wieder sein Professional Developer Training in Soli…
Scrum  from twitter_favs
7 days ago by reinhard_codes
Developers Should Abandon Agile
No matter what framework or method your management thinks they are applying, learn to work this way:

Produce running, tested, working, integrated software every two weeks, every week. Build your skills until you can create a new fully operational version every day, twice a day, multiple times a day.
Keep the design of that software clean. As it grows, the design will tend to become complex and crufty. Resist and reverse this tendency consciously, refactoring in tiny continuous steps, all the time, so that your rate of progress is as steady and consistent as possible.
Use the current increment of software as the foundation for all your conversations with your product leadership and management. Speak in terms of what’s ready to go, and in terms of what they’d like you to do next.
agile  scrum  critique  project-management 
8 days ago by Mekk
In Search of a Servant Leader
“When the teams they work with are successful, they do not take the credit for the work. Equally when the teams they work with are not successful, the do not lay the blame at the team but work to understand what went wrong and how they can help the team improve.

So in searching for an example of a Servant Leader that people could relate to, I came to think of them as a black hole – You can’t actually pinpoint them as a separate entity but you can spot them by the effects they’re having on others around them.”
leadership  business  scrum 
8 days ago by kevinrood

Copy this bookmark:





to read