/explore
|
You are here 
|
www.uservoice.com | ||
| | | | |
sboots.ca
|
|
| | | | | "Agile" gets mentioned enough in digital government work that can sometimes seem like it applies to everything: is anything not agile? But there's a deeper meaning behind it that's easy to miss: adding agile practices without removing established, "waterfall" processes that slow a team down is a recipe for frustration. Being agile means choosing one approach over another, and deliberately prioritizing what you spend your time on. | |
| | | | |
frederickvanbrabant.com
|
|
| | | | | You can have a fantastic team of subject matter experts and brilliant technical people, but if they don't talk to each other, you will never get a good product or outcome for a project. | |
| | | | |
www.stum.de
|
|
| | | | | [AI summary] The author reflects on their extensive experience with various software development methodologies, emphasizing the importance of adapting Agile principles to fit specific project needs rather than rigidly following prescribed rules. | |
| | | | |
www.softdevtube.com
|
|
| | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | ||
