Difference between revisions of "Agile Scrum"

From Klenwell Wiki
Jump to navigation Jump to search
Line 3: Line 3:
 
Here's a selection of Hacker News comments that quickly distills for me the wisdom of the ages when it comes to project management and software development:
 
Here's a selection of Hacker News comments that quickly distills for me the wisdom of the ages when it comes to project management and software development:
  
First, see this thread for what you want to avoid:
+
What makes scrum special? Three awesome core ideas:
 +
 
 +
* https://news.ycombinator.com/item?id=17187057
 +
 
 +
See this thread for what you want to avoid:
  
 
* https://news.ycombinator.com/item?id=17511850
 
* https://news.ycombinator.com/item?id=17511850
Line 30: Line 34:
  
 
* https://news.ycombinator.com/item?id=15133593
 
* https://news.ycombinator.com/item?id=15133593
 
How do you get there? Here's as good an explanation of Scrum and why to use it as I've seen anywhere:
 
 
* https://news.ycombinator.com/item?id=17187057
 
  
 
Finally, here's a cheat sheet on outsourcing for when that conversation comes up:
 
Finally, here's a cheat sheet on outsourcing for when that conversation comes up:
  
 
* https://news.ycombinator.com/item?id=15831784
 
* https://news.ycombinator.com/item?id=15831784

Revision as of 22:41, 9 June 2021

What is Agile Scrum? For me, it's how to do software development right. Which doesn't mean you can't do it wrong. But if done right, it's your best chance of doing it right. And even then it probably doesn't work sometimes.

Here's a selection of Hacker News comments that quickly distills for me the wisdom of the ages when it comes to project management and software development:

What makes scrum special? Three awesome core ideas:

See this thread for what you want to avoid:

I like this comment in particular:

My advice: Prefer queues and continuous delivery to deadlines and unrealistic expectations.

Want to see what you really need to avoid. Money extractors:

But that problem is probably outside your control.

Also, beware expertise. It's cheap and easy nowadays. Learn the Lesson of the Windows Shutdown Crapfest:

Study the data. Listen to your users. But the best way to discover the real requirements for your software? Build it and have them use it:

What are you aiming for? A high-performing organization where everyone enjoys working together. Here are some principles:

Finally, here's a cheat sheet on outsourcing for when that conversation comes up: