Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Dev Incubator @ WDS
Transcript of Dev Incubator @ WDS
(Real) Software Engineering
A Software Engineering Adventure
"Software Engineering (SE) is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, and the study of these approaches"
Building stuff that
Building stuff that people
stuff by learning from the stuff we built last time
HTML + CSS
Ruby on Rails
Make more money
Self Care Framework
On Device Applications
On Device configuration
Android OTA Provisioning
Device Management servers
Mobile Device Management
APIS & Feeds
What *is* that stuff?
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
Simplicity--the art of maximizing the amount
of work not done--is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.
What does a software developer do?
Talk about code
Fight about code
Estimate how long it will take us to do that stuff
Think about code
Ask our customer what they want us to do
Release our code
...as often as we can
Ask ourselves how we can do that stuff better
Fix our code
...hopefully not too often
Talk to other teams about the stuff we do
Talk to the rest of the business about what they need
Help product owners figure out what they need
Innovate on new ideas
Teach ourselves new stuff
Teach our teammates about new stuff
Test our code
6 months long
1 week in 4 spent with the Dev team
2 weeks intensive at the end
Learn from, and be part of, the team
Project/s to work on throughout the time
Support from the team and Dev mentors in the other 3 weeks
Dev laptop and resources
Primed for a Dev job at the end