PedroGeoGISdev wiki
  • Home
  • Linux OS
    • Linux: concepts
    • Linux: basic concepts
    • Linux: Bash
    • Linux: su and sudo
    • Linux: pipes
    • Linux: File System
    • Linux: Virtual Machines

    • Linux: distros
    • Linux Distros: Ubuntu
    • Linux Distros: Mint
    • Linux Distros: Debian
    • Linux Distros: openSuse
    • Linux Distros: Manjaro
    • Linux Distros: Red Hat Enterprise

    • Linux: laboratories
    • Linux Lab#LI01-1: Choose Linux
    • Linux Lab#LI01-2: Install at least three distributions
    • Linux Lab#LI01-3: Adjust user permissions
    • Linux Lab#LI02-1: Export env user with grep and pipe
    • Linux Lab#LI03-1: Manage users and groups
    • Linux Lab#LI03-2: Manage files
    • Linux Lab#LI03-3: Manage software
    • Linux Lab#LI03-4: Manage hardware
    • Linux Lab#LI04-1: Bash scripting, qtool
    • Linux Lab#LI04-2: Bash scripts as terminal tool
    • Linux Lab#LI04-3: Distribute the terminal app

    • Linux readings
    • Linux Resources
  • DevOps
    • What is DevOps
    • DevOps: Introduction
    • DevOps: Agile and Microservices
    • Infrastructure as code (IaC)
    • Immutable Infrastructure
    • Software Lifecycle

    • Documentation
    • How to document: Quarto and Obsidian

    • Network protocols
    • Network: Basics
    • Network: Client-server
    • Network Protocols
    • Network: DNS
    • Network: API Rest
    • Network: gRPC
    • Network: Websocket
    • Network: SMTP
    • Network: Ping
    • Network: UDP
    • Network: webhook
    • Network: SOAP
    • Network: graphQL

    • Version Control
    • Git
    • GitHub
    • Idea and GitHub 2023
    • Git and GitHub 2023 CLI

    • IDEs
    • IDE: Visual Code
    • IDE: IntellJIdea

    • DevOps tools
    • Amazon Web Services AWS
    • Docker
    • Jenkins pipelines
    • Kubernetes k8s
    • Digital Ocean
    • Nagios
    • Ansible

    • DevOps Laboratories
    • Lab 1: chat App
    • Lab 2: Spring Boot AWS AEB manually
    • Lab 3: Spring Boot and AWS S3 publisher
    • Lab 4: Spring Boot Docker/Jenkins
    • Lab 5: k8s on Digital Ocean
    • Lab 6: Spring Boot AWS codecommit

    • DevOps readings
    • DevOps Resources
  • MarkUp
    • MarkUp Languages
    • Introduction Markup
    • HTML Markup
    • Markdown Markup
    • Markdown and HTML working together, good idea?

    • Quarto Markdown
    • Quarto Markdown: basics
    • Quarto Markdown: creating
    • Quarto Markdown: publishing
    • Quarto Markdown: code & data
    • Quarto Markdown: api rest call
    • Quarto Markdown: OJS Cells
    • Quarto Markdown: cheat-sheet

    • Styling: CSS
    • Cascade Style Sheet
    • Cascade Style Sheet: Box Model and Containers
    • CSS: W3.css

    • MarkUp Languages Laboratories
    • Lab#MD01-1: Create and publish by Quarto

    • MarkUp Languages readings
    • MarkUp Languages Resources
  • Java SE
    • What is Java SE
    • Java Standard Edition: Basics
    • Java Standard Edition: Principles
    • Java MOOC Helsinki
    • Java MOOC Helsinki Syllabus

    • Java Create Project
    • Java SE: Maven
    • Java SE: Create Maven Project
    • Java SE: Project push GitHub
    • Java SE: JUnit and TDD

    • Java Concepts
    • Java SE: Class and Objects
    • Java SE: Scope
    • Java SE: static modifier
    • Java SE: Coupling and DDD
    • Java SE: Packages
    • Java SE: Abstract/Interface
    • Java SE: Java 8

    • Java Principles
    • Java SE: Encapsulation
    • Java SE: Abstraction
    • Java SE: Inherence
    • Java SE: Polymorphism

    • Java Design Patterns
    • Java Patterns: UML
    • Java Patterns: Types
    • Singleton
    • Factory
    • Abstract Factory
    • Builder
    • Facade
    • Bridge
    • Decorator
    • Composite
    • Observer
    • Strategy
    • State
    • Commander

    • Java SE Laboratories
    • Lab#SE00-1: Maven Person
    • Lab#SE00-2: Maven Clinic
    • Lab#SE00-3: Library Model
    • Lab#SE00-4: Abstract/Interface Human
    • Lab#SE01-1: Maven/Gradle Person and Account
    • Lab#SE01-2: Maven/Gradle Person and Account stored in JSON
    • Lab#SE02-1: Movie/Review, Model
    • Lab#SE02-2: Movie/Review, CRUD Operations
    • Lab#SE02-3: Movie/Review, factory
    • Lab#SE02-4: Movie/Review, interactivity and coupling
    • Lab#SE02-5: Movie/Review, simulate interactivity by console
    • Lab#SE03-1: Library/Book, Core-Model
    • Lab#SE03-2: Library/Book, Sprint Zero
    • Lab#SE03-3: Library/Book, Expand Model
    • Lab#SE04-1: healthyFood Restaurant, Core Model

    • Java SE readings
    • Java SE Resources
  • Python
    • Python Basics
    • Python: Basic Concepts
    • Python: Tips
  • JavaScript
    • JavaScript Basics
    • JavaScript: Basic Concepts
    • JavaScript: Tips
  • Spring
    • Spring Legacy
    • Spring Framework
    • Spring MVC
    • Springs Servlets

    • Spring Boot Basics
    • Spring Boot: fundamentals
    • Spring Boot: create a Project
    • Spring Boot: H2 DB and Thymeleaf
    • Spring Boot: cycle

    • Spring Boot Concepts
    • Spring Boot: Dependency Injection
    • Spring Boot: Annotations
    • Spring Boot: Controller
    • Spring Boot: View
    • Spring Boot: Thymeleaf
    • Spring Boot: Vaadin Flow
    • Spring Boot: Vaadin Hilla
    • Spring Boot: Model
    • Spring Boot: Rest
    • Spring Boot: Data & DB
    • Spring Boot: JPA & DI
    • Spring Boot: JPA Mappings
    • Spring Boot: JPA Relationships
    • Spring Boot: JPA Queries
    • Spring Boot: JPA Inherence
    • Spring Boot: Scaling

    • Spring Boot Laboratories
    • Lab#SB00-1: Library UML
    • Lab#SB00-2: CRUD User
    • Lab#SB00-3: LibraryManagement
    • Lab#SB00-4: API Rest
    • Lab#SB00-5: Rest & JPA-H2
    • Lab#SB00-6: Rest & MongoDB
    • Lab#SB00-7: Styling
    • Lab#SB01-1: DataBase
    • Lab#SB02-1: JPA Relationships
    • Lab#SB03-1: APIs & cloud
    • Lab#SB04-1: JPA Inherence
    • Lab#SB05-1: API Rest
    • Lab#SB06-1: employeeCourse
    • Lab#SB07-1: monitor Book
    • Lab#SB08-1: Restaurant UML
    • Lab#SB08-2: Vaadin
    • Lab#SB08-3: H2 and API Rest
    • Lab#SB08-4: JPA
    • Lab#SB08-5: Test API Rest
    • Lab#SB09-1: SpringIO Conference

    • Spring Boot readings
    • Spring Boot Resources
  • ReactJS
    • ReactJS: Principles
    • React JS: Introduction
    • React JS: render virtual DOM
    • React JS: Create a React project
    • React JS: Components
    • React JS: JSX
    • React JS: props and state

    • JavaScript: web scripting
    • JavaScript: basics
    • JavaScript: functions
    • JavaScript: objects
    • JavaScript: variables
    • JavaScript: flux control

    • ES6: ECMAScript 6
    • React JS ES6: arrow functions
    • React JS ES6: import modules
    • React JS ES6: array, data and key
    • React JS ES6: destructuring
    • React JS ES6: spread operator

    • ReacJS 18: Hooks
    • React JS: Rules of Hooks
    • ReactJS: useState
    • React JS: useReducer
    • React JS: useRef
    • React JS: useEffect
    • React JS: useContext
    • ReactJS: useMemo
    • ReactJS: custom hooks

    • ReactJS: Designing an App
    • React JS App: async
    • React JS App: events
    • React JS App: router
    • React JS App: conditional render
    • React JS App: styling

    • React JS: Laboratories
    • Lab#RE01-1: API Rest Axios
    • Lab#RE02-1: Router & Hooks
    • Lab#RE03-1: to-do app
    • Lab#RE03-2: HighCharts
    • Lab#RE03-3: API Rest Mono
    • Lab#RE03-4: API Rest Domains
    • Lab#RE03-5: data management
    • Lab#RE04-1: todo & server
    • Lab#RE04-2: Spring Boot & ReactJS
    • Lab#RE05-1: chat & websockets
    • Lab#RE05-2: chat: backend
    • Lab#RE05-3: chat & AWS
    • Lab#RE05-4: chat: test ws AWS
    • Lab#RE05-5: chat & front
    • Lab#RE05-6: chat & ws: front
    • Lab#RE06-1: healthyFood Restaurant
    • Lab#RE06-1-PR: create a pull request
    • Lab#RE07-1: traffic lights simulation

    • React JS readings
    • ReactJS Resources
  • Learning
    • Vocabulary
    • General Vocabulary
    • SCRUM Vocabulary
    • DevOps Vocabulary
    • Java SE Vocabulay
    • Spring Boot Vocabulary
    • DataBase Vocabulary
    • ReactJS Vocabulary
    • Web Vocabulary

    • Learning
    • Useful Questions
    • Learning: tips
    • Writing
    • Taking Notes
    • Comments
    • Document
    • Auto-Evaluate

    • Books & Articles
    • Books
    • Articles

    • What is SCRUM
    • SCRUM Agile Methodology
    • Agile Manifesto & Values
    • SCRUM Guide

    • Scrum Steps
    • Meetings, Impediments and Iterations
    • User stories, Tasks and Habits
    • Delivering Value & Communication
    • ScrumMaster, how it works
    • Mindset, the key to everything
    • Product Owner, how it works
    • Managing Time & Mind
    • Team & the Specialist
    • Albertus’ Dilemma
    • Before SCRUM
    • Team Dynamics
    • Emotions and Thoughts
    • Decision Making and Intuition
    • Beyond SCRUM
    • Balances, atmosphere and tools

    • Resources
    • SCRUM Resources
  • QGIS
    • QGIS basics
    • QGIS: basic concepts

    • QGIS laboratories
    • QGIS Laboratory 1: Introduction to Open Source GIS
  • ArcGIS Pro
    • ArcGIS Pro basics
    • ArcGIS Pro: basic concepts

    • ArcGIS Pro laboratories
    • ArcGIS Pro Laboratory 1: Getting Started
  • Bookmarks
    • Online Resources
    • Online Resources
  • About
    • About me and this site
    • About me
    • About this site
    • About images credit
  • Email
  • GitHub
  • LinkedIn
  1. Scrum Steps
  2. Balances, atmosphere and tools
  • Vocabulary
    • General Vocabulary
    • SCRUM Vocabulary
    • DevOps Vocabulary
    • Java SE Vocabulay
    • Spring Boot Vocabulary
    • DataBase Vocabulary
    • ReactJS Vocabulary
    • Web Vocabulary

  • Learning
    • Useful Questions
    • Learning: tips
    • Writing
    • Taking Notes
    • Comments
    • Document
    • Auto-Evaluate

  • Books & Articles
    • Books
    • Articles

  • What is SCRUM
    • SCRUM Agile Methodology
    • Agile Manifesto & Values
    • SCRUM Guide

  • Scrum Steps
    • Meetings, Impediments and Iterations
    • User stories, Tasks and Habits
    • Delivering Value & Communication
    • ScrumMaster, how it works
    • Mindset, the key to everything
    • Product Owner, how it works
    • Managing Time & Mind
    • Team & the Specialist
    • Albertus’ Dilemma
    • Before SCRUM
    • Team Dynamics
    • Emotions and Thoughts
    • Decision Making and Intuition
    • Beyond SCRUM
    • Balances, atmosphere and tools

  • Resources
    • SCRUM Resources

On this page

  • 1 Clients
  • 2 How to collaborate with clients?
    • 2.1 Atmosphere
    • 2.2 Balances
      • 2.2.1 Creativity vs. Productivity
    • 2.3 Tools
  • 3 Agile Holistic Approach
  • 4 References
  • Edit this page
  • Report an issue
  1. Scrum Steps
  2. Balances, atmosphere and tools

Balances, atmosphere and tools

SCRUM Step 15

scrum
balances
Clients often struggle to articulate their needs precisely, but that’s not a hitch. The key is, they can pinpoint what resonates with their vision.
Author

albertprofe

Published

Tuesday, June 1, 2021

Modified

Sunday, August 10, 2025

📘 Summary: SCRUM Step 15 - Balances, atmosphere and tools

Clients may struggle to express needs precisely, but their ability to recognize alignment with their vision is pivotal.

Payment is the acknowledgment of unspoken needs being met, forging a collaborative agreement.

In client interactions, impediments are viewed as feedback, guiding decision-making towards optimal solutions. Good decisions yield positive feedback or client endorsement through payment, affirming optimal solutions. Agile teams require an atmosphere conducive to open communication, balanced dynamics, and effective tools for informed decision-making.


Keywords: SCRUM Step 15 - Balances, atmosphere and tools

Clients, Articulation of Needs, Payment as Approval, Collaboration, Feedback as Impediments, Decision-Making, Agile Teams, Atmosphere, Balances, Tools, Optimal Solutions, Creative Thinking, Innovation, Productivity



1 Clients

What do clients want?

What do clients want?

Clients often struggle to articulate their needs precisely, but that’s not a hitch. The key is, they can pinpoint what resonates with their vision.

Copywriting Secrets is a book about how everyone can use the power of words to get more clicks, make more sales, and get more subscribers… no matter what you sell or who you sell it to!

It’s not about what they say; it’s about what they recognize.

Payment is the stamp of approval—they pay when they see that alignment. It’s a dance of understanding, where their vague ideas meet tangible solutions.

In this collaboration, the transaction isn’t just for a product or service; it’s the acknowledgment of their unspoken needs being met. It’s like nodding to an unspoken agreement—you get what they want, even if they can’t put it into words.

2 How to collaborate with clients?

In client interactions, we recognize impediments not as roadblocks but as invaluable feedback.

Note

Deciphering this feedback is key, as it serves as a compass for steering our decision-making toward optimal solutions.

The essence lies in a symbiotic relationship—good decisions yield positive feedback or, more directly, client endorsement through payment, the ultimate affirmation of an optimum solution.

Understanding that bad decisions translate to adverse feedback, and the worst decisions often result in silence, underscores the critical importance of honing our decision-making prowess.

Agile teams need three crucial elements at the forefront: atmosphere, balances, and tools, to excel in this endeavor.

2.1 Atmosphere

Firstly, fostering an atmosphere conducive to open communication and idea exchange is paramount. An environment where team members feel free to voice concerns and suggestions ensures that feedback is constructive rather than stifled. To achieve this:

  • establishing clear boundaries,
  • implementing simple rules,
  • and selecting the right profiles are essential.

2.2 Balances

Secondly, striking the right balances is foundational. Whether it’s the delicate equilibrium:

  • between fixed, growth, and survival mindsets,
  • of anti-fragility and lateralization,
  • of addressing the intricate dynamics of identity, change, moral emotions, emotions and status games.
  • of the nuanced interplay of productivity versus creativity, achieving equilibrium is the linchpin of informed decision-making.

2.2.1 Creativity vs. Productivity

We live in a world that’s obsessed with ‘getting stuff done.’ Everyone wants to know how to be more productive, and yes, productivity at work is important.

But does this emphasis on becoming better, faster, and stronger leave any room for creative thinking at work?

Being creative is often associated with the arts, while innovation is a buzzword of the tech world. However, fostering a culture of creativity and innovation can benefit companies of all shapes, sizes, and areas of expertise. Developing new processes, improving workflows, and solving problems are all forms of creativity.

2.3 Tools

Thirdly, providing teams with the right tools amplifies their capacity to dissect complexities and make well-informed decisions. These tools encompass:

  • frameworks like SCRUM,
  • time-boxing,
  • planning poker,
  • iterations,
  • goals and a long etcetera.

In essence, our journey toward optimal decision-making entails recognizing impediments as integral feedback loops, refining our understanding through a dance of balances, and equipping agile teams with the right atmosphere and tools.

This holistic approach ensures that our decisions resonate positively with clients, translating challenges into opportunities for growth and innovation.

3 Agile Holistic Approach

Agile Holistic Approach
Stage Core Description Content Challenges Tools
#0 Networked Knowledge Knowledge creation and acquisition How to Learn, how to recognize core knowledge and connect it The knowledge illusion, burnt out, no being pareto: lost energy/time Lateralization, time-boxing, learning atmosphere, the a-ha moment
#1 Productivity & Execution 4-events SCRUM iteration Meetings, Impediments, Iterations, (1) planning, (2) execution, (3) review, (4) retrospective Boycotts, hidden agendas, bad meetings, bad time-boxing, not applying SCRUM Scrum Glossary, Team Dynamics, stories, tasks, team atmosphere
#2 Creativity & DecisionMaking Make the rights steps towards client’s unspoken desires Decision Making & Strategic thinking Find out the right decision at the right moment. It is key when it is done in real-time, incomplete info and unknown consequences at long term Intuition, Creativity, Divagation, Mindset

4 References

  • Creativity vs. Productivity
  • Is the Quest for Peak Productivity Killing Creativity?
Back to top
Beyond SCRUM

This website is built with Quarto.

Difficulties are just things to overcome, after all. Ernest Shackleton

  • Edit this page
  • Report an issue