Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
BenLinders
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
by
BenLinders
7y ago
Something is seriously wrong if the Scrum master doesn't take feedback. That goes against the Agile values and principles.
2.
▲
by
BenLinders
7y ago
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.
3.
▲
by
BenLinders
7y ago
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.
4.
▲
Rebuild or Refactor, what to choose?
(infoq.com)
6 points
by
BenLinders
11y ago
|
0 comments
5.
▲
More Feature Branching Means Less Continuous Integration: Do You Agree?
(infoq.com)
1 points
by
BenLinders
11y ago
|
0 comments
6.
▲
by
BenLinders
11y ago
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.
7.
▲
The Pitfalls That You Should Always Avoid When Implementing Agile
(infoq.com)
1 points
by
BenLinders
11y ago
|
1 comments
8.
▲
by
BenLinders
11y ago
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 s
9.
▲
Challenges When Implementing Microservices and Why Programming Style Matters
(infoq.com)
1 points
by
BenLinders
11y ago
|
1 comments
10.
▲
Developing Provably-Correct Software Using Formal Methods
(infoq.com)
1 points
by
BenLinders
11y ago
|
0 comments
11.
▲
by
BenLinders
11y ago
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 a
12.
▲
by
BenLinders
11y ago
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.
13.
▲
by
BenLinders
11y ago
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 understa
14.
▲
by
BenLinders
11y ago
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.
15.
▲
New community to write and discuss code with fellow programmers
(infoq.com)
3 points
by
BenLinders
12y ago
|
0 comments
16.
▲
How Futurespectives Help Teams to Reach Their Goals
(benlinders.com)
1 points
by
BenLinders
12y ago
|
0 comments
17.
▲
by
BenLinders
12y ago
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
18.
▲
Is Unhedged Call Options a Better Metaphor for Bad Code?
(infoq.com)
1 points
by
BenLinders
12y ago
|
0 comments
19.
▲
by
BenLinders
12y ago
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
20.
▲
by
BenLinders
12y ago
Anybody wants to share his/her experiences with Exercism.io?
21.
▲
Improve Your Programming Skills with Exercism.io
(infoq.com)
1 points
by
BenLinders
12y ago
|
1 comments
22.
▲
Spice up your Agile Retrospectives
(benlinders.com)
1 points
by
BenLinders
12y ago
|
0 comments
23.
▲
Mixing Agile with Waterfall for Code Quality
(infoq.com)
1 points
by
BenLinders
12y ago
|
0 comments
24.
▲
Empower Teams to Increase Quality
(benlinders.com)
1 points
by
BenLinders
12y ago
|
0 comments
25.
▲
Dealing with Negative Issues in Retrospectives
(tech.d8p.it)
1 points
by
BenLinders
12y ago
|
0 comments
26.
▲
Documentation in Agile: How Much and When to Write It?
(infoq.com)
2 points
by
BenLinders
12y ago
|
0 comments
27.
▲
Coaching by Just Being There
(benlinders.com)
1 points
by
BenLinders
12y ago
|
0 comments
28.
▲
A Management 3.0 Workout Summary in 15 Tweets
(benlinders.com)
1 points
by
BenLinders
12y ago
|
0 comments
29.
▲
We're shipping: Valuable Agile Retrospectives on Amazon and Lulu
(benlinders.com)
1 points
by
BenLinders
12y ago
|
0 comments
30.
▲
Alternative Approaches for Implementing Agile
(infoq.com)
2 points
by
BenLinders
12y ago
|
0 comments
More ›