Daniel Lynn Lukas Klose. Technical Practices Refresher

Transcription

1

2 Daniel Lynn Lukas Klose Technical Practices Refresher

3 agile principle #3 Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. agile principle #9 Continuous attention to technical excellence and good design enhances agility.

4 Technical Debt

5 Technical Debt and Value New Value Bug Maint Improve Time

6 Technical Debt and Value New Value Bug Maint Improve Time

7 Technical Debt and Value New Value Bug Maint Improve Time

8 Technical Debt Strategy Policy Practice

9 Seven Technical Practices to Start With

10 Refactoring Don t touch that system, it might break. Don t even look at it!

11 Refactoring We all make mistakes. We don t have to live with them.

12 Refactoring A refactor is a change made to the internal structure of software to make it easier to understand and cheaper to modify without changing its observable behavior.

13 Refactoring Key Benefits: v Change Happen. Let s make it easy! v Loosely-coupled code reduces risks of accidental impacts. (@Scale+) v Refactoring is a key part of paying down your technical debt

14 Test-Driven Development (TDD) That definitely used to work...

15 Test-Driven Development (TDD)

16 Test-Driven Development (TDD) Key Benefits: v Tackles work little-by-little ideal for complicated problem v Complex application build from simple behaviors v Working Software is the Primary Measure of Progress v Development is focused on and targeted at test cases v Creates a large set of automated test cases easy to find out if you accidentally affected code elsewhere in the application (@Scale+)

17 Behavior-Driven Development (BDD) That may be what I asked for, but that s not what I meant.

18 Behavior-Driven Development (BDD) BDD Interaction Business Function TDD Integration Code Logic

19 Behavior-Driven Development (BDD) 42 Hill Street Allentown PA Ford Prefect

20 Behavior-Driven Development (BDD) Given I am checking out And I m at the payment stage When I enter an invalid CC Number Then I am immediately alerted of the problem And Submit is disabled

21 Behavior-Driven Development (BDD) Key Benefits: v Ensures that the stakeholders and development team have the same expectations before we start coding (@Scale+) v It s easy to add new cases or examples as we discover them (@Scale+) v Working Software is the Primary Measure of Progress v Development is focused on and targeted at test cases v Creates a large set of automated test cases easy to find out if you accidentally affected code elsewhere in the application (@Scale+)

22 Continuous Integration and Delivery (CI/CD) It works on my machine.

23 Continuous Integration and Delivery (CI/CD)

24 Continuous Integration and Delivery (CI/CD) Key Benefits: v Fast feedback in integration errors (@Scale+) v Creates a common build platform similar to production v Allows a platform for automated tests and static code analysis to run on v Constant deployment means deployment is never scary v Promotes simple and consistent deployment processes and environments v Encourages safe coding practices (when going to production)

25 Pair Programming Two brains are better than one.

26 Pair Programming Two people code together. Done

27 Pair Programming I removed the embedded video for size reasons. You can find it at:

28 Pair Programming Key Benefits: v More brains on the problem leads to: v Faster problem solving v Fewer silly human errors v Knowledge sharing on the team! v 4 eyes see better than two!

29 Spike I don t even know where to start!

30 Spike FaceSpace Example Show me people who went to my high school Show me where they live now Show me their occupation Show my if they are married / have kids Control my hot tub

31 Spike - Characteristics A spike tackles a specific aspect of a problem with the intent to drive out unknowns or risks. 4 hrs Timebox! No points! Prototypes and demonstrable learnings is preferable to research, reading, and conversations.

32 Spike Key Benefits: v Drives out risk by trying and observing v Improves User Story Estimation reliability v Solves risk-avoidance in teams who shy away from commitment on difficult work.

33 Static Code Analysis Code Standards. I think they re documented in Sharepoint?

34 Static Code Analysis - Example Sid can play tennis as good as his brother. When you become a parent, you will think different about children. This is the type of arrant pedantry up with which I will not put.

35 Static Code Analysis Key Benefits: v Finds dangerous patterns before they become bugs (@Scale+) v Can identify age-related problems like deprecation v Most tools are configurable to support any teams standards (@Scale+)

36 Test-Driven Development Spike Refactoring Pair Programming Static Code Analysis Behavior-Driven Development Continuous Integration and Delivery

37 CSM and A-CSM Learning Objectives New Learning Objectives Added in 2017!!!

38 CSM and A-CSM Learning Objectives CSM define technical debt and explain the impact of accumulating technical debt list at least five practices that will help Scrum Teams deliver a high-quality product increment and reduce technical debt each sprint. list at least three ways technical practices may impact the Development Team s ability to deliver a potentially releasable increment each sprint

39 Technical Debt and Value New Value Bug Maint Improve Time

40 Static Code Analysis Key Benefits: v Finds dangerous patterns before they become bugs (@Scale+) v Can identify age-related problems like deprecation v Most tools are configurable to support any teams standards (@Scale+)

41 CSM and A-CSM Learning Objectives A-CSM describe at least five technical practices that will help Scrum Teams deliver a high-quality product increment and reduce technical debt each sprint. describe at least three ways technical practices may impact the Development Team s ability to deliver a potentially releasable Increment each sprint. identify at least three engineering practices that are essential when using Scrum at scale.

42 Static Code Analysis Key Benefits: Important for the A-CSM v Finds dangerous patterns before they become bugs (@Scale+) v Can identify age-related problems like deprecation v Most tools are configurable to support any teams standards (@Scale+)

43 Questions?