• Like
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
280
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
6
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Agila FrukostseminarierKnowit 2013
  • 2. Våra seminarier•  Torsdag 31/1 Produktledning & kravhantering•  Fredag 22/2 Management 3.0 - introduktion•  Tisdag 26/3 HR - nya roller med nya mål                        •  Tisdag 23/4 Projektledning•  Onsdag 15/5 Att bygga team •  Torsdag 13/6 Förvaltning och support •  Anmälan till lars.irenius@knowit.se Produktledning & krav. 2 Frukostseminarium Knowit 31/1 2013
  • 3. Agenda idag•  8:00 – 8:10 Hämta frukost och komma på plats. •  8:10 – 8:45 Agil produktledning och kravhantering –  Lars Irenius, Knowit•  8:45 – 9:15 Att hantera både förutsägbarhet och osäkerhet i produktledning. –  Johan Oskarsson, Knowit•  9:15 – 9:20 Paus•  9:20 – 9:50 Prototypdriven behovsanalys. –  Elisabeth Hagberg, Knowit•  9:50 – 10:00 Avrundning Produktledning & krav. 3 Frukostseminarium Knowit 31/1 2013
  • 4. Agil produktledning ochkravhantering.Lars Irenius, Knowit
  • 5. Krav = att överföra kunskap Produktledning & krav. 5 Frukostseminarium Knowit 31/1 2013
  • 6. Kravspec på dryck Produktledning & krav. 6 Frukostseminarium Knowit 31/1 2013
  • 7. Produktledning & krav. 7Frukostseminarium Knowit 31/1 2013
  • 8. Michael Polanyi, 1966 Produktledning & krav. 8 Frukostseminarium Knowit 31/1 2013
  • 9. Explicit, tyst och underförstådd (implicit)kunskap Tacit Produktledning & krav. 9 Frukostseminarium Knowit 31/1 2013
  • 10. Produktledning & krav. 10Frukostseminarium Knowit 31/1 2013
  • 11. Källa: http://ashklytoosi.edublogs.org/week-4/ Produktledning & krav. 11Frukostseminarium Knowit 31/1 2013
  • 12. Ikujiro Nonaka, 1995 Produktledning & krav. 12 Frukostseminarium Knowit 31/1 2013
  • 13. SECI Process Produktledning & krav. 13 Frukostseminarium Knowit 31/1 2013
  • 14. David Snowden, 1999 Produktledning & krav. 14 Frukostseminarium Knowit 31/1 2013
  • 15. Cynefin (“kuh-NEH-vin”)oförutsägbar förutsägbar Produktledning & krav. 15 Frukostseminarium Knowit 31/1 2013
  • 16. Snowbird, Utah Produktledning & krav. 16 Frukostseminarium Knowit 31/1 2013
  • 17. Agile Manifesto, 2001 Produktledning & krav. 17 Frukostseminarium Knowit 31/1 2013
  • 18. Fyra av de tolv principerna bakom AgileManifesto.Our highest priority is to satisfy the customer through early andcontinuous delivery of valuable software.Welcome changing requirements, even late in development.The most efficient and effective method of conveying information toand within a development team is face-to-face conversation.The best architectures, requirements, and designs emerge fromself-organizing teams. Produktledning & krav. 18 Frukostseminarium Knowit 31/1 2013
  • 19. Mike Cohn, 2004 Produktledning & krav. 19 Frukostseminarium Knowit 31/1 2013
  • 20. Why User Stories? (Mike Cohn)•  User stories emphasize verbal communication.•  User stories work for iterative development.•  User stories encourage participatory design.•  User stories build up tacit knowledge. Dont forget that the main purpose of a story card is to act as a reminder to discuss the feature. Keep these reminders brief. Add the detail you need to remember where to resume a conversation, but do not replace the conversation by adding more detail to the story card. Produktledning & krav. 20 Frukostseminarium Knowit 31/1 2013
  • 21. PROPS, PPS etc. BP-A BP-B BP-C Produktledning & krav. 21 Frukostseminarium Knowit 31/1 2013
  • 22. RUP Requirement ProcessStep 1: Creating an overview of your projectBegin the requirements management process by planning how to organize your project.Step 2: Analyzing the problem analyst  and  team   The   and gathering stakeholder needsThe analyst is responsiblemembers  determine  the   for analyzing and gathering stakeholder needs. These needs express the problem or businessobjectives that drive thepriority  of  the  requirements     software requirements.Step 3: Documenting features in a vision documentThe analyst and the customer agree on the high-level product requirements (or features) of the proposed software product.Step 4: Developing requirement details Team  members  use  queries  After the feature requirements have been defined, the analyst can create iews  to  review  their   use cases to implement and  vsoftware requirements or assigned  requirements  those features. The analyst enters requirements in and defines attributes to track the requirements.Step 5: Creating traceability between requirementsAfter all the requirements have been created in , the analyst uses traceability to ensure the quality and completeness of yourproducts. Traceability can indicate the source, derivation, or dependencies between requirements.Step 6: Prioritizing requirements Team  members  use  queries  The analyst and team members determine the priority of the requirements or use cases that have been created. and  views  to  track  the  Step 7: Assigning requirementsAfter you have prioritized the requirements and use cases, assign them to team members. status  Step 8: Adding detail to requirementsTeam members use queries and views to review their assigned requirements and gather information for adding detail to therequirements.Step 9: Managing changes to the requirementsTeam members use queries and views to track the status of the requirements and manage change. Source: Rational Software Information Center Produktledning & krav. 22 Frukostseminarium Knowit 31/1 2013
  • 23. Agil utveckling (SCRUM) Produktledning & krav. 23 Frukostseminarium Knowit 31/1 2013
  • 24. Jurgen Appelo, 2011 Produktledning & krav. 24 Frukostseminarium Knowit 31/1 2013
  • 25. Produktledning & krav. 25Frukostseminarium Knowit 31/1 2013
  • 26. Hur säkerställer ni enkontinuerlig dialog ? Produktledning & krav. 26 Frukostseminarium Knowit 31/1 2013