This document discusses software engineering and the software lifecycle. It covers Agile methodologies like Scrum, behaviors like test-driven development, challenges like communicating between stakeholders, and practices like code reviews, continuous integration, and automated testing. The goal is to deliver value incrementally through collaboration and an emphasis on working software.

1. Engineering Software
&
Software Lifecycle

2. Talking & Videos
Q&A (jump in anytime)
www.slideshare.net/specialised

3. Keith Mitchell
Group Engineering Manager, Future Media Sport
t: @specialized
e : keith.mitchell@bbc.co.uk

4. Lancaster University
1994 - 1997 - Undergraduate
1997 - 2011 - PhD & Research Fellow
BBC Future Media
2011+

6. NEWS
LIVE
Radio
SEARCH
WEATHER
HOMEPAGE
ABOUT THE BBC
TRAVEL
MUSIC
Bitesize
ARTS
FOOD
NEWSBEAT
PROGRAMMES

7. SPORT

14. 96 million
Brazil World Cup - The Open Championship
(12 June - 20 July)

15. 77.6 million (June)
Biggest month in our entire history
bit.ly/BBCSportRecord

16. Engineering Software
&
Software Lifecycle
Will cover People & Technology

17. Programming is easy
software development (and engineering) is hard

20. before we see why its hard to engineer software
lets cover the basics

21. Agile

22. Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

24. scrum, the basics
https://www.youtube.com/watch?v=vmGMpME_phg

25. product owner
technical project manager
business analysts
dev/engineering team
test

26. Title Text

27. estimation (Tee/poker/points/relative)
planning
velocity - burnup and burn-down
stand-up / retrospectives

28. Any questions ?

29. So....
... how do we do it? And ....
... why is it so hard?

30. We talk alot

31. Many stakeholders

32. AGILE process
EPICs & Initial User Stories
Estimation
Expand Stories
Business Analysis
Tech Investigation
Identify dependancies
Tech Architecture
Designs
Sprint Planning
3 Amigos
Daily Standups
Build
Daily Standups
Show and Tell
Retrospective
Deploy

34. The team
Communication (Tickets)
Ceremonies

35. we use of patterns / processes

36. Behaviour driven development
test driven development

37. BDD at the BBC
http://tinyurl.com/pn4hhth

38. pre
three
agree

39. Ruby & PHP App
Moving to Client-side JS
Cucumber worked for a while...

40. BA (& dev) driven change
It Should over Given, When, Then scenarios

41. Should IT
github.com/bbc-sport/ShouldIT

43. BDD + TDD
Living documentation (organic)
You know when you are done
Helps drive the design
Reliable and tested product

44. Agile
SCRUM or Kanban
3 Amigos
Definition of Ready
Definition of Done (DoD)
Dev Practices
Behaviour and Test Driven
Version Control (branch, release, trunk)
Continuous Integration
Testing and Tooling

45. Summary
Deliver value early
Generalists v Specialists & Comms
Incremental & Working - Stop at any time
Handle change - e.g. diff colour
Less waste
Faster

46. Intermission?
Digital Media Graduate Scheme - Now Open!
http://www.bbc.co.uk/careers/trainee-schemes-and-
apprenticeships/technology/digital-media-

47. Engineering Excellence

48. the day in the life of
bbc.co.uk/academy/technology/software-engineering

50. Operations
as live production
Dev
int test stage live
sandbox
shared platform
rpm rpm
A Sport
Engineer
rpm
rpm rpm
done
must be
stable &
trustable
Audience
bbc.co.uk/developer

51. Operations
as live production
Dev
int test stage live
sandbox
SPORT NEWS HOMEPAGE
shared platform
rpm rpm
A Sport
Engineer
rpm
rpm rpm
done
must be
stable &
trustable
Audience
bbc.co.uk/developer

52. Standard Services
Message Queues
Datastores
Key/Value Store
Generic Services
BBC iD / Media Players
Frameworks
Mast Head / Analytics / Logging / Monitoring
Greenhouse
secure/shared dev environment
Eclipse / NetBeans / Sublime / TextMate /
IDE / PHPStorm / WebStorm
Sandbox - VM
GitHub
Hudson / Jenkins (CI)
Maven (Project Object Models)
Confluence (wiki)
JIRA (tickets) LAMP
Linux/Apache/MySQL/PHP
- but no MySQL directly
bbc.co.uk/developer

53. bbc.co.uk/developer
ReactJS
AngularJS
Ajax
HTML
CSS
PHP (Zend)
Java (Spring)
RESTful APIs
SQL / RDF / JSON / XML

54. Engineering Excellence and ‘4 Good Things’ (TM)
Meaningful code reviews
Developers being accountable for non-functional requirements
(DoD, NFR checklist)
Continuous integration
Automated acceptance testing

55. Meaningful code reviews

57. “You know you are working on clean code when
each routine you read turns out to be pretty much
what you expected...”
-- Ward Cunningham

58. Bad code is easy to recognize.
Clean code is hard to write.
It requires discipline, courage, and skill.
Some of us are born with “Code-Sense”.
Others have to fight to acquire it.

59. reading code
reveal your intent
int d; // elapsed time in days
int elapsedTimeInDays;

60. This code isn’t complicated
BUT
not explicit
reveals no intent

61. This code isn’t complicated
BUT
not explicit
reveals no intent

63. Functions
do one thing
do it well

64. code reviews

65. Why?

66. improve quality
clarity
verification & validation
know your code base / comms
knowledge sharing
collaborative
mentoring
share best practice
consistency / standards
insigtful
increase confidence
audit trail

67. What and How?
pair programming
pull requests

68. What and How?
part of workflow
code smells

69. Consistent feature files
Linting - PHP/js/html/
Exception & Error handling
Logging
Analytics
Monitoring
Cacheable

70. Duplicated Code
Use extract or pull up patterns to refactor
and keep the camp clean!
Method/Function Length
Long methods/functions
Large Classes (with lots of instance variables)
Long Param lists & Long message chains

71. Feature Envy
showing too much interest in other classes
Invoking methods on objects to calculate values
Switch statements
these are bad

72. version control
just use it!

73. Developers being accountable for Non functional Requirements

74. NFRs part of
definition of done

75. what are NFRs

76. Performance
Scalability
Availability / survivability
Security
Consistency / reliablity
Monitoring
Reliability / Resilience
Failover/disaster recovery
Interoperability
UKFS / IFS / editions / localisation
Accessibility
24/7 Operational Support

77. Are they really NFRs?
Could they be functional?

78. e.g. Performance
Page weight
Load time (timeline)
Time to glass/first byte (TTG/TTFB)

79. e.g. accessibility
remember Ian’s talk
we can measure / automate

80. make ‘em functional
make ‘em testable!

82. Continuous integration

83. hudson / jenkins
Build the system on commit and/or nightly

85. Automated acceptance
testing

86. we test (almost) everything
we automate (almost) everything

89. viewporter
http://bit.ly/I7xZSv

91. wraith
https://github.com/BBC-News/wraith

92. sandbox live diff

93. when things go bad
no blame
just cake (or donuts)

94. Programming is easy
software development (and engineering) is hard
BUT
it’s fun / collaborative / rewarding / character building / ……

95. You & the art of engineering
team
no ‘I’ in team
test
first
TDD / BDD
tools
Git
Open
Source
texts
Uncle Bob Martin
Martin Fowler
GOF
Kent Beck

96. Thanks for your time
Keith Mitchell
Group Engineering Manager
t: @specialized | e : keith.mitchell@bbc.co.uk
BBC Digital Media Graduate Scheme
http://www.bbc.co.uk/careers/trainee-schemes-and-apprenticeships/
technology/digital-media-graduate-scheme