A while ago, Markus Eggers – Google+ started following me on G+, so I found out about his posts: most of them refer to very useful agility related ones.
So my reading list just got a bit longer, with tuples on Markus Eggers – Google+ and where it points to.
- [WayBack] Details on Zombie Scrum and it’s origin…:
- [WayBack] Zombie Scrum -LeadingAgile ; TL;DR: See Scrum “rules” as a starting point, not an end state.
- [WayBack] “How to Sell Refactoring?”
- [WayBack] How to Sell Refactoring? The Case of Nordea Bank AB; Refactoring is often not a technical challenge. Teams can accurately diagnose inefficient code design. If they have sufficient time and budget at their disposal, they would probably get things done. In this article, we focus on the strategic code refactoring. This distinction was introduced by the BNS IT consultants as part of the method called Natural Course of Refactoring.
- [WayBack] How to Avoid Daily Scrum Traps
- [WayBack] Scrum Alliance – Member Articles: How to Avoid Daily Scrum Traps; TL;DR: A paradigm shift from person-centric to work-in-progress-centric
- [WayBack] “We’re really good at knowing when we haven’t started something. We’re pretty good at knowing when we’re done with something. We’re horrible anywhere inbetween…
- [WayBack] Why Getting to Done Is So Important; TL;DR: avoid starting multiple things in parallel; make sure that at the end of each iteration, all work is either:
- Not started
- Done
- [WayBack] Why Getting to Done Is So Important; TL;DR: avoid starting multiple things in parallel; make sure that at the end of each iteration, all work is either:
- [WayBack] “Louise Elliott discusses why people tend to blame and punish others, the impact of self-blame, the unintended results from punishment, and the alternatives…
- [WayBack] “We tried that and it didn’t work.” – Choose the right tool for the task ahead… #agile #scrum
- [WayBack] We Tried That, and it Didn’t Work -LeadingAgile I once used a hammer and it didn’t work. Therefore, people should never use hammers. If you find that reasoning satisfactory, then you may also appreciate the following statements: We tried pair programming and it didn’t work…
- [WayBack] “How to introduce Agile to non-IT teams” #agile #teamwork #non-it
- [WayBack] How to introduce Agile to non-IT teams:To encourage non-IT teams to embrace Agile, you should first demonstrate the value that an Agile mindset can deliver.
- [WayBack] Estimation: Hours Versus Story Points
- [WayBack] Scrum Alliance – Member Articles; Estimation: Hours Versus Story Points: here is a comparison that highlights some benefits realized by moving to story-point estimation.
- Absolute versus relative
- Personal versus team evaluation
- Effort in hours versus size
- Abstraction
- Burn-down versus velocity
- [WayBack] Scrum Alliance – Member Articles; Estimation: Hours Versus Story Points: here is a comparison that highlights some benefits realized by moving to story-point estimation.
- [WayBack] “Don’t underestimate on-premise data center influence on your organization’s culture”
- [WayBack] Don’t Build Private Clouds – Subbu’s Blog:
- You don’t need to own data centers unless you’re special
- Private cloud makes you procrastinate doing the right things
- Private cloud cost models are misleading
- Don’t underestimate on-prem data center influence on your organization’s culture
- [WayBack] Don’t Build Private Clouds – Subbu’s Blog:
- [WayBack] “Think how powerful it would be if, rather than relying on just a few key individuals, your whole team were experts in their field.”
- [WayBack]Project Overload: Are You ‘Killing’ Your Best People?: Experts are vital to your business, but you risk losing them if they become inundated with work. So how can you use their expertise without overloading them?
- [WayBack] “5 Tips To Re-Energise Your Daily Standup”
- [WayBack] 5 Tips To Re-Energise Your Daily Standup Meetings • Girl’s Guide to Project Management some tips I really like!
- [WayBack] Who the Heck Wrote This? 3 Ways to Deal with Bad Code (is there a universal way to write good code? No, but you can limit bad code)
- [WayBack] Who the Heck Wrote This? 3 Ways to Deal with Bad Code Dealing with bad code is a daily reality for some developers. Here are some of the best—and worst—approaches to take.
- [WayBack] “Cost is easy to measure: salaries, time, tools, licenses, computers, material. But can we put a number of value?” #agile #roi
- [WayBack] ROI Is Dead!: Last month I was in Huib Schoots’ testing workshop. He talked about being asked “What’s the ROI of testing?”. To which he replied “I don’t know, what’s the ROI of management?”.
- [WayBack] “How to Create the FASTEST Teams” #agile #team #projects
- [WayBack] “User stories are not requirements”
- [WayBack] Crisp’s Blog » User stories are not requirements: Elephants are not giraffes and user stories are not requirements. They share some traits and you may find them in the same context, but that does not make them the same. Despite that, many believe that user stories are the new requirements because there has to be requirements for a project, right? I give that a double “no”, they are not requirements and that is not anything we really need. User stories are about being able to explore options and seize opportunities. Requirements are about deciding up front and sticking with that.
- [WayBack] The Water Fall Myth
- [WayBack] Herding Cats: The Water Fall Myth: a historic perspective on some software development methodologies and where they are applicable.
- [WayBack] “An Iterative Waterfall Isn’t Agile”
- (2015) [WayBack] An Iterative Waterfall Isn’t Agile Lately I’ve seen teams create an iterative waterfall process and call it agile. Here are some differences between iterative waterfall and agile.
- [WayBack] Retromat – “Planning your next retrospective? Get started with a random plan,…
- [WayBack] Planning Poker Online
- [WayBack] “No. Agile Does Not Scale. (but agility scales quite well, thank-you-very-much)”
- [WayBack] No. Agile Does Not Scale. – Jurgen Appelo – Medium (but agility scales quite well, thank-you-very-much)
- [WayBack] The Story with Story Points
- [WayBack] The Story with Story Points I don’t like story points. I think this is part of my crusade against complexity…
- [WayBack] “Unready work creates churn for the delivery team, they spend more time tryin…
- [WayBack] Definition of Ready: Creating Clarity in the BacklogLeadingAgile Just as a “definition of done” is used to create alignment across a delivery team on what it means to be done with a backlog item, the “definition of ready” provides clarity to a product owner or product owner team on what it means to create ready backlog items.
- [WayBack] The Definition of DoneLeadingAgile If you’re in the business of application development, you’ve asked that question before. So what is the definition of done? When asking the question, it’s important to note who you are and your level in the organization. Delivery teams, program teams, and portfolio teams define done differently.
- [WayBack] “Estimates on Split Stories Do Not Need to Equal the Original”
- [WayBack] Estimates on Split Stories Do Not Need to Equal the Original I’m often asked if the sum of the estimates on the smaller stories must equal the estimate on the original, larger story. The answer is no.
- [WayBack] Separate Estimating from Committing Remember the difference between an estimate and a commitment and keep the two activities separate, educating management and customers as necessary.
- [WayBack] Do What Works… Even If It’s Not Agile.
- [WayBack] Do What Works… Even If It’s Not Agile. -LeadingAgile I think I’ve come to the conclusion that ‘agile’ as we know it isn’t the best starting place for everyone that wants to adopt agile. Some folks, sure… everyone, probably not. For many companies something closer to a ‘team-based, iterative and incremental delivery approach, using some agile tools and techniques, wrapped within a highly-governed Lean/Kanban […]
- [WayBack] Tooltip Cube for Agile Meetups, User Stories and WiP limit
- [WayBack] “When you’re dealing with complex systems, failure is going to happen; it’s a given. What we do after that failure, however, strongly influences whether…
- [WayBack] “Blameless post-mortems assume that humans have good intentions in the genera…
- [WayBack] Blameless Post-Mortems Blameless post-mortems of production incidents are increasingly seen as an essential fixture of any organisation’s procedures. Mathias Meyer, from Travis CI, shared how blameless post-mortems had a profound effect on him. InfoQ took this opportunity to have a look at post-mortem practices of organizations like Etsy, GitHub or Chef.
- [WayBack] Crisp’s Blog » Priorities and WIP
Other interesting posts:
- [WayBack] “10 Career-Limiting Mistakes To Avoid”
- [WayBack] “Deadlines Always Matter”
- [WayBack] Computer Programming To Be Officially Renamed “Googling Stackoverflow”
- [WayBack] Microservices Trade-Offs
- [WayBack] “Don’t start with a monolith if you want to end up with microservices.”
- [WayBack] Don’t start with a monolith Don’t start with a monolith if you want to end up with microservices. It’s usually a good idea to follow the YAGNI principle, but a monolith won’t magically contain services waiting to be liberated.
- [WayBack] A Quick Puzzle to Test Your Problem Solving #f
- [WayBack] A Quick Puzzle to Test Your Problem Solving – The New York Times; on confirmation bias
- [WayBack] “Schrödinger’s Backup: The condition of any backup is unknown until a restore is attempted…
- [WayBack] Is it wise to use microservices? It depends…
- [WayBack] MicroservicePremium The microservice architectural style is useful for handling complex systems, but brings its own complexity so should not be used for simpler environments.
[WayBack] Is it a Bird? Is it a Plane? No, it’s a Super PMO!
- [WayBack] “Solve Puzzles using Programming Logic. ” – looks like fun, starting with puzzles for 4yr old…
- [WayBack] Preparing a meeting? Provide your suggested time and location options and let participants decide…
- [WayBack] Code commenting styles…
- [WayBack] “Noto is Google’s font family that aims to support all the world’s languages….
- [WayBack] Google Noto Fonts Google has been developing a font family called Noto, which aims to support all languages with a harmonious look and feel. Noto is Google’s answer to tofu. The name noto is to convey the idea that Google’s goal is to see “no more tofu”. Noto has multiple styles and weights, and is freely available to all. The comprehensive set of fonts and tools used in our development is available in our GitHub repositories.
–jeroen
The Wiert Corner - irregular stream of stuff 