and business happy ▰ technical and process debt elimination Believe that: ▰ Any problem must be solved at the right level ▰ Software is easy. People are hard ▰ A problem should be highlighted, an idea should be "sold", a solution should be demonstrated Last Talks: ▰ Docker for Node.js developer ▰ 5 production Node.js stories ▰ Testing in Node.js World ▰ TypeScript for Node.js applications ▰ Spec driven development in Microservices Links: Site GitHub Twitter Facebook 2
will be too big. ▰ In their own specification – nobody will read. ▰ In Acceptance Criteria for specific story – regression testing will be very difficult. ▰ In special backlog AKA Technical backlog – this is our approach!
business model where “Developers are always scapegoats“ ▰ You live in perfect world ▰ You work in a startup company ▰ There is Chuck Norris in your development team ▰ You hide real picture from customer
that describes the functionality supporting the user-facing features in User Stories. ▰ It contains the team members expectations about project needs. ▰ describes what the user does with the software and how the software responds. A User Story is a functional requirement that resembles a use case and test case. ▰ It contains the product owner expectations about customers needs.
stories ▰ Non-functional requirements ▰ Demo for development team ▰ Delivery as artifact (package, document, etc) ▰ Consist of users stories: As a <persona> I want <goal> So that <reason> ▰ Functional requirements ▰ Demo for PO and stakeholders ▰ Delivery as working software
new microservice or Database. ▰ Team Infrastructure. For example, new feature for CI ▰ Refactoring. Changes in codebase for improving maintainability. ▰ Bug fixing. ▰ Spike. When it’s time for R&D adventure
of not solving the problem 3. Make sure that decision makers aware that this is a problem and know the assessment 4. Generate solution(-s) and estimate(-s) 5. Get a confirmation