How to convince your client/supervisor/team to your ideas? – this is one of the most common questions that come up during my work with teams. In this article you will learn effective techniques that will help you propose solutions that you think are better than those suggested by your client. We will also decide if it is really about convincing. (You may find useful to look into previous parts of the series: Part1, Part2, Part3, Part4, Part5)...
Read more at InfoQ
agile
(41)
anti-patterns
(17)
architecture
(33)
books
(10)
buissness analysis
(1)
cases
(1)
code speaks 2u
(3)
communication
(1)
conferences
(13)
consulting
(1)
conversation patterns
(26)
customer collaboration
(14)
ddd
(5)
design patterns
(15)
desing
(1)
dialogi
(1)
dsl
(2)
effectiveness
(19)
embedded
(1)
events
(22)
gtp
(4)
info
(2)
infoq
(5)
kanban
(2)
lean
(2)
master
(1)
measuring
(1)
orm
(2)
pea
(2)
product humanisation
(1)
refactoring
(13)
requirements
(7)
retrospections
(1)
retrospective
(1)
scrum
(9)
scrumguide
(1)
sm
(1)
soft skills
(4)
software craftsmanship
(14)
tdd
(1)
team
(20)
time management
(3)
tutorial
(1)
uml
(1)
user stories
(1)
visions
(28)
Showing posts with label infoq. Show all posts
Showing posts with label infoq. Show all posts
Friday, January 8, 2016
Wednesday, October 14, 2015
NVC for Agile Developer
Nonviolent Communication (NVC) is an approach developed by Marshall Rosenberg to assist in caring for this chemistry during conversations. From a technical point of view, NVC is a method of conducting dialogues.
However, apart from specific techniques, it advocates a set of assumptions and beliefs that might motivate you to think of NVC as a philosophy of treating another human being – and a philosophy where verbal communication is the exact medium.
Read more at InfoQ: Conversation Patterns for Software Professionals - Part 5
However, apart from specific techniques, it advocates a set of assumptions and beliefs that might motivate you to think of NVC as a philosophy of treating another human being – and a philosophy where verbal communication is the exact medium.
Read more at InfoQ: Conversation Patterns for Software Professionals - Part 5
Friday, January 16, 2015
Conversation Patterns for Software Professional. Episode #3
Finally InfoQ published third part of Conversation Patterns for Software Professional planned serie. In case you missed the previous two there linked to my profile.
Now I have some work with the second edition of my book, so I give the articles a break for about six moths and then I look at next set of three articles.
Now I have some work with the second edition of my book, so I give the articles a break for about six moths and then I look at next set of three articles.
Saturday, November 22, 2014
InfoQ: Conversation Patterns for Software Professionals. Part 1
InfoQ Team picked my article Conversation Patterns for Software Professionals to publication. Enjoy the piece! Next episode is coming soon.
Friday, May 2, 2014
InfoQ: *-Driven* do not change anything
InfoQ Team has published my aricle *-Driven* do not change anything.
I gave a speech on these theses during the 33rd Degree Conference 2013 and I was told I didn't know Domain Driven Desing at all. Well, I have my private opinion about this. But I am sure I know how the cognitive biases work and all that *Driven* madness is one of them.
This article is not intended to criticize anybody or anything. It is about priorities and searching for a balance. Being focused on our basic skills first, helps to use a *-Driven* approach properly especially in an unknown context. I do really appreciate all those mental frameworks because they do great job. But I think if software development is driven by something, these are stakeholder needs and our common sense. Being driven by anything else might be harmful simplification.
Enjoy the article!
I gave a speech on these theses during the 33rd Degree Conference 2013 and I was told I didn't know Domain Driven Desing at all. Well, I have my private opinion about this. But I am sure I know how the cognitive biases work and all that *Driven* madness is one of them.
This article is not intended to criticize anybody or anything. It is about priorities and searching for a balance. Being focused on our basic skills first, helps to use a *-Driven* approach properly especially in an unknown context. I do really appreciate all those mental frameworks because they do great job. But I think if software development is driven by something, these are stakeholder needs and our common sense. Being driven by anything else might be harmful simplification.
Enjoy the article!
Subscribe to:
Posts (Atom)