Hitting the Links
675 views | +0 today
Follow
Hitting the Links
A loose collection of Agile and Scrum articles
Curated by Peter Steiner
Your new post is loading...
Your new post is loading...
Scooped by Peter Steiner
Scoop.it!

Avoiding Distractions While Programming

Avoiding Distractions While Programming | Hitting the Links | Scoop.it
If you have read Getting Things Done, then you can already guess what I’m about to write here: use your inbox. If you haven’t read Getting Things Done, the
Peter Steiner's insight:
More thoughts leading me towards Kanban
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Scrum Vs. Kanban

Lately, I hear these questions a lot - “Is Scrum better or Kanban?”, “What is more suitable for my project - Kanban or Scrum?”. These questions and sometimes t…
Peter Steiner's insight:
I think the longer I'm on a Scrum team, the more I prefer to think in terms of Kanban.
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

How to Create the FASTEST Teams | All About Agile

How to Create the FASTEST Teams | All About Agile | Hitting the Links | Scoop.it
Focused & Flexible
Autonomous
Small
Talented
Established
Stable
Together
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Using “Given-When-Then” to Discover and Validate Requirements

All product partners benefit when we use efficient discovery practices to optimize each delivery. "Given-When-Then" is a powerful 2-for-1 technique you can use in structured conversations to both discover (explore) and validate (confirm) that the right product will be correctly delivered.
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Agility is a Strategy. Agile is a Tactic.

Agility is a Strategy. Agile is a Tactic. | Hitting the Links | Scoop.it
My concern with an even stronger focus on practice is that it would lead to even more Cargo Culting than we see already. People simply copying practices they see and hear about in the hope that implementing them by the book will magically lead to them being Agile.
Peter Steiner's insight:

We are uncovering better ways of developing software by doing it and helping others do it.

Through this work, our strategies have become to:

* Empower teams around economies of flow

* Reduce the batch size of value delivery

* Explore the evolutionary potential of solutions

* Sense and respond to feedback

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Learning Agile Software Development the Hard Way | You'd think with all my video game experience that I'd be more prepared for this

Peter Steiner's insight:

Great collection of links to excellent resources.

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

mca blog [three keys to design-time governance: protocol, format, and vocabulary]

mca blog [three keys to design-time governance: protocol, format, and vocabulary] | Hitting the Links | Scoop.it
so, there you have it. protocol, format, vocabulary. get those three right and you will be laying the important foundation for an IT shop that can retain stability without rigidity; that can adapt over time by adding new protocols, formats, and vocabularies without breaking existing sub-systems or ending up in a deep hole of technical-debt.
Peter Steiner's insight:

More architecture than Agile/Scrum.

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Scrummaster Resources and References

Scrummaster Resources and References | Hitting the Links | Scoop.it
This resource is new and under continual improvement. Please let us know if you experience any bugs or issues.
Peter Steiner's insight:

Be sure to check the resources and references for product owners and developers. There is a lot here!

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Who Really Wins Microservices?

Who Really Wins Microservices? | Hitting the Links | Scoop.it
Bad behavior arises when you abstract people away from the consequences of their actions
Peter Steiner's insight:

The real success stories of a microservice architecture are about how organisations that embrace small, cross-functional teams that engage with a flat, self/peer-management structure, are able to scale and innovate at levels unheard of in traditional organisational structures.

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

How Much For This Software? - Yegor Bugayenko

The very attempt to estimate a software project has fundamental flaws and can't be done right; instead, we should estimate different parameters.
Peter Steiner's insight:

<quote>My point is that instead of asking how much a software project will cost, you should ask how much software we can create for each dollar you give us and what quality will it be.</quote>

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Listen, Test, Code, Design OVER Sprints, Scrums, and ScrumMasters | You'd think with all my video game experience that I'd be more prepared for this

1. You need a shared understanding of what problem the software is intended to solve. We have learned that the best way to do this is to engage directly with the relevant situation and people.
2. You need a shared understanding of what the solution needs to do to solve the problem. We have learned that the best way to do this is through conversations leading to agreed examples and then iterating.
3. You need to build the solution. We have learned that the best way to do this is in a thoughtful, collaborative, disciplined way.
4. You need to manage the growing complexity of the system to ensure that it continues to be easy to change. We have learned that the best way to do this is as an ongoing exercise reflecting the best knowledge we have at each point.

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Home | Scrum Guides

What is Scrum?

Scrum is a framework for developing and sustaining complex products. This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together. Ken Schwaber and Jeff Sutherland developed Scrum; the Scrum Guide is written and provided by them. Together, they stand behind the Scrum Guide.
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

This is why you never end up hiring good developers

This is why you never end up hiring good developers | Hitting the Links | Scoop.it

TL;DR

1 Many interview techniques test skills that are at best irrelevant to real working life;
2 you want somebody who knows enough to do the job right now;
3 or somebody smart and motivated enough that they can learn the job quickly;
4 you want somebody who keeps getting better at what they do;
5 your interview should be a collaborative conversations, not a combative interrogation;
6 you also want somebody who you will enjoy working with;
7 it’s important to separate “enjoy working with” from “enjoy hanging out with;”
8 don’t hire assholes, no matter how good they are;
9 if your team isn’t diverse, your team is worse than it needed to be;
10 accept that hiring takes a really long time and is really, really hard.

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

How to handle unfinished User Stories in Scrum - codecentric Blog

How to handle unfinished User Stories in Scrum - codecentric Blog | Hitting the Links | Scoop.it
Have you heard of Berlin’s new airport? Landing of the first plane was originally expected for 2007, then for 2010, later it was 2011, 2012, 2013,… – and making a long story short: the grand opening party for 2017 was just postponed for an undefined time. Whether we talk about building airports or about building... Read more
Peter Steiner's insight:
Bottom line: no points awarded for unfinished stories. Slice vertically, thinner, with better understanding, prior to commitment.
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

4 steps to solving issues in projects | All About Agile

4 steps to solving issues in projects | All About Agile | Hitting the Links | Scoop.it
Agile techniques for managing and solving issues in projects
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

It's Not Just Standing Up: Patterns for Daily Standup Meetings

It's Not Just Standing Up: Patterns for Daily Standup Meetings | Hitting the Links | Scoop.it
Daily stand-up meetings have become a common ritual of many teams. However, there are many subtle details that distinguish effective stand-ups and a waste of time.
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Scrum Breakfast: What's the difference Scrum or Kanban?

How has Kanban influenced my teaching of Scrum?
I have recognized a couple of things:
The easiest route to change starts with an agreement of the parties involved.
If people look at how they work today, its well represented by Kanban
If people think back to their best projects, they find a lot of commonality with Scrum. This recognition creates often creates a willingness to try Scrum.
As it is primarily an attitude and a visualization tool, Kanban is applicable in some contexts where Scrum is not.
As it is primarily an attitude and a visualization tool, Kanban does not directly address the people issues, especially at the team level.
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Context, rationale, and overview of Story / Impact Mapping | You'd think with all my video game experience that I'd be more prepared for this

Context, rationale, and overview of Story / Impact Mapping | You'd think with all my video game experience that I'd be more prepared for this | Hitting the Links | Scoop.it
Peter Steiner's insight:

If you've only focused on user stories, you may find yourself with a "bag of leaves" and no longer see the tree they came from. Article introduces Story/Impact Mapping.

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

9 Agile Estimation Techniques

9 Agile Estimation Techniques | Hitting the Links | Scoop.it
Agile estimation techniques are collaborative.
Peter Steiner's insight:

Check out the principles of estimation: agile estimation techniques are designed to be fast, deliberately trade off accuracy because estimation is a non-value added activity that should be minimized.

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

“When will it be done?” | The Agile Management Blog

“When will it be done?” | The Agile Management Blog | Hitting the Links | Scoop.it
“So you’re the agile guy,” using a tone which sort of left me feeling like a suspect who has just been targeted and painted with lasers. He then asked the question in the forefront of his mind “When will it be done?”
Peter Steiner's insight:

“From what I know, no one has done a good job answering that to date.” Not knowing much about the project, but wanting to provide context, I followed up by saying “Agile methods will help us be able to tell you what is done which is the strongest evidence we might have to when it will be done.”

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Agile Planning in a Nutshell - Agile Advice

Agile Planning in a Nutshell - Agile Advice | Hitting the Links | Scoop.it
Agile Planning can be simple to do. Find out a simple process and a few principles to do effective Agile Planning.
Peter Steiner's insight:

1) Speed over accuracy

2) Collaborative techniques

3) Relative units

more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

Pitfall of Scrum: Problem-Solving in the Daily Scrum - Agile Advice

The Daily Scrum should be used to create transparency in the team. The Daily Scrum is meant to be short and is not a problem-solving meeting.
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

How to implement Hypothesis-Driven Development

How to implement Hypothesis-Driven Development | Hitting the Links | Scoop.it
We believe

What functionality we will develop to test our hypothesis? By defining a ‘test’ capability of the product or service that we are attempting to build, we identify the functionality and hypothesis we want to test.

Will result in

What is the expected outcome of our experiment? What is the specific result we expect to achieve by building the ‘test’ capability?

We will know we have succeeded when

What signals will indicate that the capability we have built is effective? What key metrics (qualitative or quantitative) we will measure to provide evidence that our experiment has succeeded and give us enough confidence to move to the next stage.
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

15 Useful Pacts for Agile Teams: An Agile Team Creed | The Agile Management Blog

15 Useful Pacts for Agile Teams:  An Agile Team Creed | The Agile Management Blog | Hitting the Links | Scoop.it
Simply gathering individuals together and assigning them the label of “team” does not make a team. Each team is comprised of unique personalities and thus there is no cookie-cutter best answer for every team. Each team must find its own way and navigate the uniqueness of each individual to determine the best way to handle interactions that work for their team dynamic.
more...
No comment yet.
Scooped by Peter Steiner
Scoop.it!

JIRA is Not Agile

JIRA is Not Agile | Hitting the Links | Scoop.it
At its core, Agile is a set of Values and Principles:

….
· Individuals and interactions over processes and tools
· Working software over comprehensive documentation
· Customer collaboration over contract negotiation
· Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.

Underlying these is a mindset with a focus on self-discipline, self-organization, and adaption to change.
more...
No comment yet.