Agile related topics
Agile Driven DevOps PDF 5 Agile Rules 5 Agile Rules DevOps Case Studies DevOps Case study links Scrum Ceremonies don’t just hit the bullet points Scrum Ceremonies Dont just hit the bullet points! (Rant) 4 Great Agile Driven DevOps Books
Made a few updates to the Java Maven project with Cucumber Acceptance Test demo. The Gherkin format Acceptance Criteria is now included in the post for easy copy and past and additional details about the StackSteps class are included. See the updates here
Made a few updates to the Java Maven project with Cucumber Acceptance Test demo. The Gherkin format Acceptance Criteria is now included in the post for easy copy and past and additional details about the StackSteps class are included. See the updates here
Sprint Planning: The 60/40 Split2-4 hours of Sprint planning for each week of a Sprint should yield 60% of delivery team tasks necessary to complete a user story defined and documented prior to the SprintThe 80/20 CommitmentThe average agile team incurs 10-30% technical debt in each Sprint. Mature teams closer to 10% newer Agile teams …
In this tutorial, we will walk through creating a basic JUnit test class in Eclipse just to make sure that our environment is set up properly. We will use Test Driven Development (AKA Test First Development) to ensure that we are writing just enough code to pass our test, and not writing our test to …
Acceptance Criteria, Test Automation and Gherkin What do Acceptance Criteria, Test Automation and a Cucumber have in common? Well for the uninitiated in may seem that these 3 things have nothing in common however if you are an “Agilist” or Test Automation specialist than you are probably very familiar with the similarities. Let’s start with …
Acceptance Test Automation with Cucumber / SpecFlow in Visual Studio Read More »
Pay it Forward You can pay now or pay later but trust me you’re gonna pay! I’m talking about Technical Debt… Technical Debt like any other Debt has Interest, so you can pay now or pay later but if you pay later it will be much more expensive. See this post on the Increasing cost …
Slicing by CRUD or ISUD (AKA Slicing by Operations) Any User Stories involving a managed entity, such as a Customer, Order, Employee or Product, will almost always require some level of management functionality. This management functionality will provide the ability to perform a number of operations including at a minimum operation, such as Create, Read, …
Slicing by Input Parameter (Datatypes) In most cases a business process or whatever function that the new feature is intended to automate requires some data to perform its actions. For the sake of this discussion we will refer to this data as Input Parameters. Data of different types in most cases will need to be …
A User Story is intended to be a method of communicating business or application requirements between potentially nontechnical customers, team members who are not developers and the development / operations teams that must implement the required application or features. In other words, the User Story needs to be understood by all but still provide enough …