BenLinders
Re:How to Exit Vim
on Friday January 10, 2020 @12:23PM (#22012660)
Something is seriously wrong if the Scrum master doesn't take feedback. That goes against the Agile values and principles.
Re:How to Exit Vim
on Friday January 10, 2020 @12:21PM (#22012631)
I would not call it self destruct, rather reconstruct or adjust. If the way the team uses Scrum isn't effective, then the retrospective can be used to explore issues and adjust the way of working.
Re:How to Exit Vim
on Friday January 10, 2020 @12:19PM (#22012610)
Disagree: the team owns the retrospective, not the Scrum master. If team members aren't happy with what the Scrum master is doing, that should be addressed in the retrospective.
More Feature Branching Means Less Continuous Integration: Do You Agree?
Re:The Pitfalls That You Should Always Avoid When Implementing Agile
on Monday July 06, 2015 @08:16AM (#9838508)
Moving from traditional project management to agile is a paradigm shift. This article discusses the role that management plays in organizations that have decided to adopt agile.
The Pitfalls That You Should Always Avoid When Implementing Agile
Re:Challenges When Implementing Microservices and Why Programming Styl...
on Monday July 06, 2015 @07:55AM (#9838410)
InfoQ interviewed Fred George about how make microservices as small as possible, challenges when implementing microservices and how to deal with them, why programming style matters, and what developers can do to develop their code writing skills.
Challenges When Implementing Microservices and Why Programming Style Matters
InfoQ interviewed Fred George about how make microservices as small as possible, challenges when implementing microservices and how to deal with them, why programming style matters, and what developers can do to develop their code writing skills.
Developing Provably-Correct Software Using Formal Methods
Re:The Failure of Agile
on Thursday May 14, 2015 @03:54PM (#9547204)
These are clear symptoms of not having retrospectives facilitated in a proper Wat. A good facilitator uses different exercises, has people focused on a fixed scope or time period to catch learning points, supports a team in coming up with actions that they can do immediately and that are small enough to finish on a short notice.
Re:The Failure of Agile
on Thursday May 14, 2015 @03:00PM (#9546896)
It takes a different mindset to make changes happen (agile or not). If people resists changing their mindset, nothing will happen and we keep struggling. That's a choice I'd rather not do.
Re:The Failure of Agile
on Thursday May 14, 2015 @02:57PM (#9546878)
Very true, it's not the format but the goal of adapting that matters. If you can discuss and fix your problem in a stand-up, do it. If you need to sit down for half an hour, take time for it. If you need 1/2 day to really understand what is happening and get a shared view to decide what to do, plan it. But make sure that you take action.
Re:The Failure of Agile
on Thursday May 14, 2015 @02:55PM (#9546866)
It's even worse, since you don't retrospect it's not even modified. It becomes a fixed process, and non adaptable processes simply do not work.
New community to write and discuss code with fellow programmers
How Futurespectives Help Teams to Reach Their Goals
Re:How to perform a good agile retrospective
on Monday January 19, 2015 @12:10PM (#8912776)
I think that one of the key things to make retrospectives valuable is to use suitable exercises. By valuable I mean exercises that help teams to better understand what has happened and to take action. Suitable will often depend on the team and situation at hand.
The retrospective facilitator (often the scrum master) should have a toolbox of retrospective techniques, and be able to pick the most effective one. Some of the techniques to do retrospectives are asking questions, state your feelings with 1 word, 5 times why (Root Causes) or asking why, solution focused/strengths and retrospective of retrospectives.
@BenLinders Co-author Getting Value out of Agile Retrospectives
Is Unhedged Call Options a Better Metaphor for Bad Code?
Re:Bad code isn’t technical debt, it’s an unhedged call option
on Wednesday December 24, 2014 @07:43AM (#8792628)
Want to know what Steve Freeman and Chris Matts have to say about call options or technical debt? Read http://www.infoq.com/news/2014/12/call-options-bad-code
Re:Improve Your Programming Skills with Exercism.io
on Wednesday December 24, 2014 @03:49AM (#8792151)
Anybody wants to share his/her experiences with Exercism.io?