1.000 lines of CloudFormation YAML with just 15 lines of Java code?
Say hello to the AWS CDK (Cloud Development Kit) using @java 👋
With the Level 3 Constructs (patterns) you can create an entire AWS architecture with almost no effort 👇
@ades_tweets Jag håller med om ovanstående. Mycket av problemen ligger i viljan till riktig förändring. Det är ganska lätt att introducera morgonmöten, artefakter och övriga ceremonier, men betydligt svårare att förändra de traditionella rollerna i projekt och utvecklingsteam.
There's nothing in any Agile practice framework or philosophy that says that you shouldn't document. However, writing documentation that's obsolete the moment it's written is just waste. The solution is to write code that doesn't require formal documentation. 1/
Sprint planning is an in-depth conversation that you have w/ your users to flush out the details of the story you're about to implement. Nothing wrong with that. Staring at Jira and shouting out story points is a tragedy, but that's not Sprint planning.
@mikewcohn That normally is not true. The best way is to delay until you can man the project sufficiently to take it from start to finish with as little overhead as possible in terms of context switching. Running many initiatives in parallel is what kills throughput. So I disagree.