Jazoon Day 3

Jazoon is an annual convention for java and software development in Zurich . I’m having the opportunity to attend it and I decided to blog about the experience.

Because of the overwhelming material I’m going to be writing only short notes and buzzwords (brain dumps). The intent is to mediate the buzzwords of today’s software development market.

Here is a brain dump of Day-3.

Day-3 Keynote :

Agile: how to gat started from day one. Agile chartering ,Energize your project liftoff

@dianaofportland

• Teambased work.
• Workprocess design.
• Extreme programming.

Chartering model:

• Inspiring Purpose .
• Collaborative Alignment .
• Dynamic Context.

 

Charter-Ring.

• Iterative .
• Always in draft.
• Dynamic.

Inspiring Purpose:

• Inspirational.
• Significance.
• Motivational.
• Success.
• The book: drive.
• Product vision.
• Team mission.
• Mission tests
• Everything in agile is test driven. Incremental success.
• Vision. Mission. Mission test
• More about conversations.

 

Collaborative Alignment:

• Make sure all team members work together smoothly.
• Handling crash of ideas
• Unity
• Trust building
• Collaboration
• Commitment
• Values and principels
• Core Team
• Working agreements.

 

Values of the team from Complexity science.Simple rules every member of the flock obeys.

• Match speed of other memebers
• Avoid collision with other memebers
• Always move twords the center of the team
• Don’t make more than 5 working agreements otherwise pwople forget them.

Context:

• How things go on with the team.
• How the team interact with others
• See the system
• Understand the fit.
• Recognize risk.
• Boundries and interactions
• Committed resources
• Prospective analysis.

 

• Empathy map.
• Boundery diagrams.
• Impact vs probability xy 2d diagram

Software teams are about learning code,customer needs, . . . Etc.

Book. Liftoff launching agile teams and projects.

 

Session: Software product creation.
An introduction to product management for programmers.

How software comes into existance.?

• Recognize problem.
• Design non.trivial solution.
• Confirm design with potential customers.
• Write S/W.
• Test S/W.
• Publicize.
• Sell S/W.
• Money appears !

Product life cycle

Tasks of a product manager:

• Gather information
• Determines buisiness challenges
• Work with product designers to craft solutions
• Every product must have a vision. And could be involving many people.
• Defines use cases.
• Represents the customers to the engineers.
• Represents the engineers to the rest of the organization.
• Sets expectations to the field.
• Verticle vs Horizontal industries.

Elements of product management:

Answer Questions:

• Whose problem does it solve ? Jobs. Old. Persona.
• who is paying for it.?
• Who do you compete with it?
• What the barrier of entry?
• What else is required for the ‘whole product’ and where will it come from?
• What is the sales strategy? The services and support strategy? Sales force team. App store. Sw retailer.

Customer input.

• Continual.
• Focus on problems to solve rather specific solutions.
• Gather data . How does the cuatomer live. Challenges. Sucess metrics.
• Aggregated. Yet not too generic.
• Documented. Tell stories talk to developer.

Messaging

• Why your product?
• Story telling
• Precise language is critical.
• customer terminology
• concision. Infamous elevator pitch
• clarity. Avoid bus. Jargon
• ambiguity has a gigh cost. But sometimea invisible cost.

Product design:

• Custoerm process and roles.
• Product or feature.
• Overlap with design)ux: maintain holistic vision.

Roadmap planning.

• Most task.role .expectation for product management.

Pricing

• Enterprise sw has to have a high cost. To link employees suceas to its success.

Packaging

• Faster always wins. Performance and delivery
• Consumabilty. How much effort made by the customer.

User experience and design.

• Build in terms of intended users experience.

Mistakes.

• Do not be a victim of your own conversationmis mgmnt of expectations.
• Mgmnt by feature list.
• Not established credibility
• Not having plan B.

 

Session . Android phone home.
Slidwshare.net

• The web of things.
• Arduino
• Processing. Eclipse. Netbeans.
• Atmega based
• Sunspots
• Open-picus. Flyport

 

• Android ADK
  • Android 2.3.4
  • Mega adk
  • High cost
  • Complex

• Android ADB
  • Microbridge library
  • Shield
  • import the ADB library