• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile Injection, Varberg
 

Agile Injection, Varberg

on

  • 377 views

 

Statistics

Views

Total Views
377
Views on SlideShare
371
Embed Views
6

Actions

Likes
0
Downloads
1
Comments
0

2 Embeds 6

http://www.linkedin.com 3
https://www.linkedin.com 3

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • out of reach: * too hard to setup * Singletons * Interfaces without proper classes
  • Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas
  • XP: Customer ON SITE
  • Stubb with verification method
  • Stubb with verification method

Agile Injection, Varberg Agile Injection, Varberg Presentation Transcript

  • Agile Injection Varberg 2011-04-01
  • This work by Fredrik Wendt is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License http://creativecommons.org/licenses/by-nc-sa/3.0/
  • Outline
    • Agile Manifesto
    • Scrum
    • Extreme Programming
    • Software Craftmanship
    • Parprogrammering
    • Testdriven utveckling
    • Retrospective
    • Systemförvaltning
  • Fredrik & Janne
  • Agile
  • Mythical Man Month
    • ”Adding manpower to a late project makes it later.”
    • Surgical Team
    • The Architect
    • Implementers
    • Growing software – not building?
    • One always has, at every stage ... a working system
  • Waterfail
  • Pragmatic Programmer
    • Fight software rot
    • Test ruthlessly
    • Broken Window
    • Reflect and practice
    • Automation
  • Ken Schwaber
    • 1990s + Jeff Sutherland
    • Appendix A
    • Återkom
  • We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
  • Agile Manifesto Individuals and interactions Working software Customer collaboration Responding to change
  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan
  • Continuous Delivery Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • Changing Requirements
      Welcome changing requirements , even late in development. Agile processes harness change for the customer's competitive advantage.
  • Working Software
      Deliver working software frequently , from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  • Biz & Dev Interaction
      Business people and developers must work together daily throughout the project.
  • Motivated Individuals
      Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  • Efficient Communication
      The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  • What is Progress?
      Working software is the primary measure of progress .
  • Sustainable Development
      Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  • No Technical Debt
      Continuous attention to technical excellence and good design enhances agility.
  • Do The Right Things, Only
      Simplicity – the art of maximizing the amount of work not done – is essential.
  • Self-organizing Teams The best architectures, requirements, and designs emerge from self-organizing teams.
  • Self-organizing Teams At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  • Vad hände sen?
  • Scrum
    • Product Owner
    • Team
    • Scrum Master
    • Product Backlog, Items
    • Sprint Backlog, Tasks
    • Sprint planning
    • Daily Standup
    • Sprint Review (demo)
    • Sprint Retrospective
    • Definition of Done
    • Impediments
    • Backlog grooming
  •  
  • XP
    • Rules on Planning, Managing, Designing, Coding, Testing
    • Customer always available
    • Write code to standards
    • Code the unit test first
    • Pair program prod.code
    • Integrate often
    • Collective ownership
  •  
  • Vad hände sen?
  •  
  • TDD & Coding Dojo
    • ttd-introduction-alt.odp