Archive for the ‘Agile’ Category

@kjscotland talk #agileday

September 19, 2013

Does the system have potential for the future.
Heuristics is focus of talk

Point is to get organizations to learn.

Dave Snowden

20130919-113947.jpg

cognitive-edge.com — rules is rules

Also Daniel Kahneman Thinking Fast and Slow

Roger Martin book: the knowledge funnel

Situations change so have to revisit the Algorithm.

The Black Swan logic.

20130919-115413.jpg

20130919-115839.jpg

Getting to shared understanding using ways to visualize work.

Definition of Done or Ready — are policies, makes constraints.

No constraints are chaos. People may have own set of policies, but no shared understanding. Want some constraints, but loose constraints.

Employee satisfaction if low you will not achieve potential because of high turn over.

Consciously explore the potential of a system. Amplify things we want to do more of. (retrospective).

Kanban as looking as limiting work in progress extended to the level of continuous improvement.

20130919-120623.jpg

September 19, 2013

4 levels to connect: talk, power, intent, energy

Emotional queues for our too transactional conversations.

Brother observed we tweet at each other+people say hi to ea other in elevator

Practice new language, practice having and owning a point of view.

Widen lens; narrow lens. Contemplate the opposite. Switch from problem to solution.

Position, relationship, expertise, body, charisma

Body Power: how comfortable do I feel in my own skin? Physical does count.

Focus is on position power. About knowing social position.

Intent: thinking how you want you want to affect your audience. Create the affect you desire. Pick a simple verb.

Choose the social role you play.

Examine your internal blueprint of what it means to be a professional. If you don’t consciously figure out, we will do subconsciously anyway.

Energy: connecting with big energy, example of chakras and NLP and using this to connect to others.

Live Notes and A-ha’s from #agiledaynyc

September 19, 2013

“Stop Communicating; Start Connecting” is today’s theme.

Achim Nowak Keynote: the importance of energy connections and fact of connection to physical body. Avignon ports open in the firewall.
Mary Poppendieck: develop your awareness mind so autonomic mind takes over with expertise when has to move fast. By the same token, if one wants to behave in kindness must PRACTICE.
Karl Scotland: No constraints are chaos. People may have own set of policies, but no shared understanding. Want some constraints, but loose constraints.

Live Notes @andersramsay #scrumnyc #agile #eurorscgny 7/19 7 pm

July 19, 2012

Anders Ramsay speaking at the Scrum NYC User Group, using a beta version of his Agile 2013 workshop.

My comment: One of the major questions that has come up in training I have personally taken is devs saying the stories are not “detailed enough.” In this talk/workshop Anders presents a way to solve this issue — and make better software by considering UX — using varieties of user stories.

First, elicit Experience Stories that state the problem versus a solution. Experience Stories ask “what is the source problem or goal?” (This is often emotional, not easy estimable, testable, etc.)

Dev Stories answer “What we should build.”

Feature stories answer features we would like.

Not that stories are written three times, but evolve, and even UX has been considered.

Elicit Experience Stories > glue together with UX design

(Anders ran Innovation Game of Speedboat @lukehohmann )

Anders on personna:
– find four or five quirks
– use a person that is *not* an average Joe-Blow
– don’t use a picture, don’t spend time.
– not clinical, scientific, more utilitarian

Use Design Studio
– establish focus and boundaries
– warmup /raw materials
– sketching in a time box
– pitch / critique

Card storming write as many possible features down as possible.

Then based on cards, do story mapping.

UI then shows whats missing and enables effective sizing of stories. Story maps reveal features that should be in UI.

Customers do not know how to size cards. Work with dev to slice features into cards.

Putting “why” at the center gives us the “so that” of a user story.

Size of stories can be confusing. What’s our destination? If too big to decompose.

A vision story has a different purpose.

Level of detail needed is determined by person building it, and juxtaposed with cost.

Could “dot voting” skew? Story points not same. It is about trending in current moment. Story points attach costs.

Anders believes scrum puts too much weight on product owner. Jeff talking about this at Agile 2012. Product owners should be dictators inside a democracy. Democratize prioritization to extent you can. PO should not be writing stories.

Rob Purdie commented: Scrum has demanded PO involvement deeply. Depends on organizational maturity. Otherwise the PO swoops in at beginning / end.

Anders: no matter what PO says, it may not lead to product success. ( Via Lean Startup)