Paul Sizemore » PMM

Artefakter af Agile Development

Paul Sizemore — Wed, 07 Mar 2012 14:51:06 +0000

Anything produced in business that is not used in the finished good or service is an artifact, and requirements are artifacts. Requirements are essential, også. Because of this it is important to create the minimum documentation needed to communicate the requirements. Many times the business solutions group, or a consulting firm, feels it is paid by the word.

Large enterprises, such as Humana and SiriusXM, have traditionally excelled at creating excessive artifacts. Sometimes it’s needed, to help in an audit situation. But, often, it’s a byproduct of the culture, and doesn’t directly serve the product development process.

This leads to enormous Word requirement documents in excess of 100 pages, that the teams avoid. Instead of looking at requirements as documentation, it is important to look at them as communication. It’s also helpful to have it in a form that the teams enjoy going to, they can get in and out quickly. They can find the information they need.

A switch to Jira, http://www.atlassian.com/software/jira/overview, can put the infrastructure and tools in place to make that organizational change.

Tilmelding på Meetup for ProductCamp DC

Paul Sizemore — Mon, 20 Feb 2012 15:40:29 +0000

In order to signup for ProductCamp DC you will will first need to go to the event page: http://www.meetup.com/ProductCampDC/events/48130972/
The First Step) Click Join Us

Second Step) As a user that does not have a Meetup Account, or is not signed in, you will be prompted to create an account or sign in.

Step Three) If you have never used Meetup before, you need to verify Your Email Address. The browser will message you that you need to check your email. There is a message in the inbox of the email account you indicated, and you need to click the link to activate your Meetup account.

Fourth & last Step) After verifying your address, the link will take you to the ProductCamp DC event registration. You’ll get the chance to fill out the event profile. Be sure to include your Twitter if you have one.

Ny ProductCamp DC stedet på udvikling

Paul Sizemore — Mon, 13 Feb 2012 00:18:54 +0000

The ProductCamp DC team is creating a new web site to replace the older Webnode site. We have decided on a WordPress site, and to use the P2 theme, found at http://wordpress.org/extend/themes/p2. The theme is clean and modern.

P2 is the theme that I am currently using on this site, and it’s extremely easy to use.

We’ve started to refine messaging to Register, Sponsor, and Volunteer. This aligns with the three primary personas that I see, the attendee, the executive that will sponsor, and the person that will be an active volunteer.

ProductCamp DC Placering annonceret

Paul Sizemore — Fri, 03 Feb 2012 19:37:43 +0000

The next ProductCamp DC on May 5, 2012 is going to be at CustomInk, located in Tysons Corner, VA. It will be easier in & out than Network Solutions was, needing people to check in as they entered.

Sign Up

View Larger Map

Hvad gør en Humana Product Owner Må?

Paul Sizemore — Tue, 10 Jan 2012 18:52:35 +0000

At the Humana Innovation Center the product owner responsibilities include representing the customer voice in the Scrum or Kanban team, og er ofte den eneste stemme for kunden. SW, jo stærkere Product Owner er, jo mere vil produktet være det flugter med en historie, Epics, Temaer og produkt Vision. Alt for ofte, med en svag produkt ejer, brugeroplevelsen fortyndes i bestræbelser på at udvikle holdet. Deres mål er at par historier, og opretholde den største hastighed kan de. Dette udgør et punkt i konflikt mellem produktet ejeren, and the rest of the Scrum Team.

Fungere som en mentor til produktet ejeren, vi fik engang at vide, at det ville tage fem story points for at fuldføre, hvad der var en grundlæggende PHP include, og det gik uimodsagt i Scrum, indtil udgangen, da jeg talte op. Med udfordring, it was quickly lowered to a one.
Jeg ser Scrum som en kamp, en kamp mellem produktet ejeren og dev, og idet undertal, the product owner needs to be able to spot problems.

Produktet ejer tager Key Feature & Epics, skriver støtter historier, and presents them to the Scrum team.

Produktet ejer er ansvaret er:
• Hvis du vil skrive historier, og sørg for at de spores i efterslæbet
• prioriterer efterslæbet, i henhold til produkt strategi
• Hjælper Scrum Master & Team i Release & Sprint Planning
• Selv om de bor i dag-til-dag produktoplysninger, de rådgive om temaer og Vision
• accepterer eller afviser det arbejde, som udviklingsgruppen
• En interessent kommunikation (i dette aspekt de beskytter holdet)
• De kan opsige sprint
• De taler på vegne af kunden, og er kundens Champion

Vigtigst, the Product Owner is ultimately responsible for the success of the product.

ProductCamp DC: An Unconference

Paul Sizemore — Sat, 07 Jan 2012 18:32:55 +0000

ProductCamp DC is an open source conference to teach, network and participate in the DC community of Product Managers, Product Marketers, and entrepreneurs. The cost of ProductCamp DC is your participation, there are no ticket costs. Just bring your ideas, expertise and enthusiasm. You are asked to volunteer in some capacity, either leading a session, facilitate a panel discussion, take video, or bring something unique to ProductCamp DC.

Stay in contact with ProductCamp DC:

WebSite:
Twitter:
Facebook:
Meetup:
LinkedIn:

Best Practices i kodning: Et udgangspunkt

Paul Sizemore — Sun, 25 Dec 2011 16:36:24 +0000

When starting development on a new product, it’s often important to establish guidelines of best practices. In the attached, best practices for the Intranet development at Finish Line.

Practices.docx

Customer Retention Program: Et start sted

Paul Sizemore — Sun, 25 Dec 2011 16:16:14 +0000

Flash var i sin vorden, og her er vi, på Finish Line, anvender det til kundens belønninger og fastholdelse. This as an early iteration of a user experience built for Rewards Members.