Archive for the ‘Methodology’ Category

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)

The Missing Agile Principle @agileuxnyc @giffconstable

February 25, 2012

He is finding lots who talk about doing; less doing. (reminds me of dinner conversation with Jeff Patton).

In manifesto what is “value?”. Look at VC definition–might be end customer.

Know what KPIs are.

Conversation is shifted from knowing it is done to knowing it is good.

Eric Ries mentioned for validated.

UX should be the stewards of value. UX community is not talking about value. Path! Need to ground things in value.

WordPress for iPad crash again. ;(

Focus on results. And communicate in results, metrics and progress. That gives you credibility in the organization.

1 think like an owner, even in big company
2 think holistically
3 no us vs them
4 involve early and be transparency – see Pixar documentary. No egos slain. Makes people not want to show work in progress
5 people want to work on something meaningful
6 build culture of hypothesis not egos not hippo
7 mentor and get mentored across company lines (Tobias Mayer coaching complaint addressed)
8 be scrappy, don’t ask for permission, be persistent, broadcast win

Don’t fear measurement. Own results. Yes, metrics are muddy.

Ground yourself in progress.

Ultimately work is meaningless unless we provide value.

@jboogie @agileuxnyc Demystifying Design #leanux #demystify

February 25, 2012

Wow, doing a presentation while organizing conference. An example of hyper productive. 🙂

Started his career working at Circus. Had to figure out the culture. Used example of Sneetch. In one end goes requirements, other end comes Sneetches with stars on their bellies.

We like it like Wizard of Oz. Insulates us from Them. Mass can adore us from afar.

But it becomes a cancer. Everyone splits off into silos and no communication.

Everyone starts using different language. This puts PM in middle, (used Frodo as PM! 🙂 )

Transparency builds trust. Because they know what’s going on.

Robert Dailey study in Management Daily – how tight is the team. (reminds me of a tech lead saying to me “we getting the band back together?”)

Show how sausage is made.

Learn Design is a balancing act. When people collaborate, their investment goes up and quality of work goes up.

(Oh no! WordPress crash)

UX becoming facilitators.

Sometimes okay just to reveal it was just gut.

Architect for the Eden Project. Ground is being quarried. Look for TED talk.

Marc Scheff

Typekit – showing font affect right away

1 draw together
2 show raw work don’t wait for ta-da, walk them thru process
3 teach the discipline – every time you show work, teach rationale and decisions, teach the jargon
teach jargon, examples KERF carpentry, sanguineous crust is a scab, cognitive load
4 hang the work in the halls