Michel Grootjans Pascal Mestdach.  Michel Grootjans ◦ Enterprise Architect ◦

Slides:



Advertisements
Similar presentations
Iteration Planning.
Advertisements

A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.
Scrum Jarred Payne Ashrith Pillarisetti. Scrum Prepare for Project Plan the Project Plan a Sprint Run a Sprint Track the Sprint.
 What is FitNesse / Slim? (10’)  Setting up FitNesse – demo (10’)  Introduction to Snacks-R-Us (10’)  Iteration 1 (35’)  Iteration 2 (35’)  Integration.
Rational Tool Overview. Introduction Requirements-Driven Software Development with Rational Analyst Studio. Tafadzwa Nzara Analysis & Design Consultant.
Individuals and interactions
Individuals and interactions
SE 555 Software Requirements & Specification Requirements Validation.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
Managing a Project Using an Agile Approach and the PMBOK® Guide
Agile Acceptance Testing Closing the communication gap in software projects Gojko Adzic
LEARN. NETWORK. DISCOVER. | #QADexplore Implementing Business Process Management: Steps to Success WCUG – November 18, 2014.
T EAM F OUNDATION S ERVER IN D EVELOPMENT Kambiz Saremi.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Every week: Sign in at the door If you are new: Fill in Registration Form Ask a Mentor how to get started Make sure you are on the Athenry Parents/Kids.
What is Business Analysis Planning & Monitoring?
1 Design and Integration: Part 1 Nuggets about Design vs Project Management.
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
Agile Acceptance Testing Software development by example Gojko Adzic
Behaviour Driven Development with Cucumber for Java.
Software Testing Life Cycle
© BJSS Limited Going Agile UK TMF - April 2011 Mark Crowther, Test Consultant.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
Extreme programming overview Agenda  Extreme programming goals  Extreme programming values  Extreme programming practices  The Extreme programming.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
Chapter 3 – Agile Software Development Pepper modification of Sommerville presentation & Colm O’hEocha – AgileInnovation Ltd presentation 1Chapter 3 Agile.
SOFTWARE TESTING Scope of Testing  The dynamic Indian IT industry has always lured the brightest minds with challenging career.
5. Planning.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.
Michel Grootjans Pascal Mestdach.  Michel Grootjans ◦ Enterprise Architect ◦
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
2. GATHERING REQUIREMENTS Object-Oriented Analysis and Design NTPCUG.
XP Explained Chapters 7-9. Primary Practices  Sit together Ideal Resistance Multi-site  Whole Team All the necessary skills in a single management structure.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Sofia Bulgaria Summer School IST eXPERT: Best Practice on e-Project Development 30 June - 2 July 2003 eXtreme programming.
Acceptance criteria vs. Functional requirements by Anna Dąbrowska.
Software Construction Lecture 18 Software Testing.
A Few Agile Practices Or how to plan who does what over the next two weeks when Iteration I is due C Sc 335 Rick Mercer.
Automated Acceptance Testing and Continuous Delivery Larry Apke Agile Expert
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
WEP Presentation for non-IT Steps and roles in software development 2. Skills developed in 1 st year 3. What can do a student in 1 st internship.
XP Overview Short Life cycle Risky / Dynamic Requirements Increase developer productivity.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Requirements Engineering Southern Methodist University CSE 7316 – Chapter 3.
Chapter 7 The Practices: dX. 2 Outline Iterative Development Iterative Development Planning Planning Organizing the Iterations into Management Phases.
Planning for Success (aka “Avoiding Failure”) Project Planning 1.
CS 5150 Software Engineering Lecture 7 Requirements 1.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Software Development A Proposed Process and Methodology.
Stand Up Comedy Project/Product Management
Phoenix Scrum User Group Simplifying Scrum Online May 21 st 2009.
Michel Grootjans Pascal Mestdach.  Michel Grootjans ◦ Enterprise Architect ◦
Formal definitions written in the manual.  Written specification  External product of the Architect  Details what the user sees  Does not detail what.
Interactions. The prey, the pack, and the hunt Your goal is to meet your customer’s needs That goal, and nothing else, is the prey Not throwaway prototypes.
Meeting Practices Yan Wei Foundation Extreme programming is used Meeting practices are based on extreme programming technology with.
Continuous Improvement. Start Simple and Continually Improve E.g., Gmail Labels 1.
Extreme Software Engineering A Hands-On Approach From Extreme Software Engineering: A Hands-On Approach Daniel H. Steinberg Daniel W. Palmer.
User Stories- 2 Advanced Software Engineering Dr Nuha El-Khalili.
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
Testing under the Agile Method CSCI 521 Software Project Management based on the book Testing Extreme Programming by Lisa Crispin and Tip House.
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
Gojko Adzic Agile Acceptance Testing Closing the communication gap in software projects Gojko.
September 20, 2017 Agile Techniques Workshop Susan Futey
Introduction to Requirements
Coding - The Ultimate Survival Skill
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Test Driven Lasse Koskela Chapter 9: Acceptance TDD Explained
Agile Development – a new way of software development?
Presentation transcript:

Michel Grootjans Pascal Mestdach

 Michel Grootjans ◦ Enterprise Architect ◦ ◦  Pascal Mestdach ◦ Solution Architect ◦ ◦  Download material: ◦ On google code:  ◦ Checkout in svn: 

 Specification Workshop  Setup Fitnesse  Iteration 1  Iteration 2  What’s in it for you?

Mr W. Fall, CEO of BDUF Development: “Our developers are working 14 hours a day to get our latest project delivered on time.” “We need an application where they can order pizza’s, beverages, snacks,... as their evening dinner! So they can work longer!”

 We agree with Mr W. Fall to make a very basic implementation and put it into production as soon as possible.  A little sketch

 We define a product backlog with estimated user stories for planning purposes.  We prioritize the product backlog together with Mr W. Fall.  An agreement is made to develop following user stories in the first iteration of 2 weeks:

 Goal: Nail down the scope of the user stories with real world examples, which we all agree on.  Workshop Outputs: ◦ Enough realistic examples to start working ◦ Shared understanding of the domain  Some tips: ◦ Involve the whole team ◦ Don’t over complicate things ◦ Also identify edge cases and negative paths ◦ Stay focused on the user story ◦ Describe what, not how ◦ Communicate intent, explain why

 Realistic examples make us think harder  Customers or functional analysts typically think about the happy path  Developers focus on edge cases and alternative scenarios  Testers want to break / cheat the system  So, Involve the whole team!

 Scope of the user story is nailed down with real world examples  Welcome FitNesse!

 Specification Workshop  Setup Fitnesse  Iteration 1  Iteration 2  What’s in it for you?

 Latest version of FitNesse ◦ ◦ Unzip into a directory of your choice (f.e. d:\Fitnesse) .Net 2.0 testrunner ◦ ◦ Unzip to d:\Fitnesse\Dotnet2  Java Runtime Environment ◦

 Customize port FitNesse is running on  Location of java.exe  Optional: disable versioning system  run.bat: ◦ jre\bin\java -jar fitnesse.jar %1 %2 %3 %4 %5 -p 8888 –e 0  stop.bat: ◦ jre\bin\java -cp fitnesse.jar fitnesse.Shutdown %1 %2 %3 %4 %5 –p 8888

  !path classes !path fitnesse.jar !path dotnet2\*.dll !define COMMAND_PATTERN {%m %p} !define TEST_RUNNER {dotnet2\FitServer.exe} !define PATH_SEPARATOR {;}

 Specification Workshop  Setup Fitnesse  Iteration 1  Iteration 2  What’s in it for you?

Testing values Easily

Batch comparisons

 Specification Workshop  Setup Fitnesse  Iteration 1  Iteration 2  What’s in it for you?

Your own test language

 3 Suites in Fitnesse ◦ Prepared Test Suite – tests for next iterations ◦ Work In Progress – doesn’t break the build ◦ Acceptance Suite – breaks the build!

 Specification Workshop  Setup Fitnesse  Iteration 1  Iteration 2  What’s in it for you?

 Developers will actually read the specifications  They will understand the stuff correctly  They will not skip parts of the spec  You can track the development progress  Save time on acceptance/smoke testing

 Requirements will be unambiguous and without functional gaps  Business analysts will really understand those special cases you mentioned  You will have automated tests to guide development  It will be easier to take-over and hand-over code

 Finally stop those guys from making the same mistakes over and over  Avoid doing the same stuff all the time  Build quality in from the start  Verify business rules by a click on a button

acceptance-testing-into-the-development-process/

 Books  On the web ◦ ◦ ◦ ◦ /13/fitnesse-and-the-three-way.aspx /13/fitnesse-and-the-three-way.aspx  Yahoo Group ◦