SlideShare a Scribd company logo
A Force of One - Agile and the Solo Developer
A Force of One - Agile and the Solo Developer
A Force of One - Agile and the Solo Developer
A Force of One - Agile and the Solo Developer
A Force of One - Agile and the Solo Developer
What are the practices relevant to a solo developer?



How can we tell if we’re winning?



Where should I start first?
A Force of One - Agile and the Solo Developer
A Force of One - Agile and the Solo Developer
Vision document
User stories
Single project backlog
Customer contact
Browse Catalog           Biz Value: 5   Acceptance Criteria:

As a shopper I want to browse the       − Shopper is shown a list of product
Tailspin Toys catalog so that I may       categories.
purchase some toys.                     − Shopper can view details for each
                                          product in catalog, including :
                                           name, inventory #, description,
                                           price, and related items.


Estimate: 3
A Force of One - Agile and the Solo Developer
Colocation
Relative size estimates
Small batch sizes
Continuous integration
Frequent releases
Research spikes
Relative size
estimates
Small
batch sizes
Test driven requirements
Test driven development
(Red-Green-Refactor)
Done Done state
Bugs before features
Emergent architecture
Simple design (YAGNI)
Aggressive refactoring
(green code only)
Simple
design
(YAGNI)
Simple
design
(YAGNI)
Single project backlog
Information radiators
Customer demos
A Force of One - Agile and the Solo Developer
A Force of One - Agile and the Solo Developer
Coding standards
Automated functional
tests
Sustainable pace
Sustainable
pace
A Force of One - Agile and the Solo Developer
Collaboration with customer
Attention to quality
Incrementalism
Automation
Continuous improvement
Energized workforce
No definitive process
Huge cases
Technical debt
Large, complex, high-risk
projects
A Force of One - Agile and the Solo Developer
User stories
Single project backlog
Relative size estimation
Small batch sizes
Simple design (YAGNI)
Sustainable pace
A Force of One - Agile and the Solo Developer
https://tfspreview.com/
Buckaroo Banzai
A Force of One - Agile and the Solo Developer
A Force of One - Agile and the Solo Developer

More Related Content

A Force of One - Agile and the Solo Developer

Editor's Notes

  1. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/ipoxstudios/6264081801/
  2. MotivationAutonomy
  3. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/mandmandt/5501371830/
  4. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/23653627@N03/2280134052/
  5. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/oskay/893848036/
  6. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/visualpanic/5942994577/
  7. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/visualpanic/5942994577/
  8. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/tomsaint/3752937440/
  9. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/seeveeaar/2035597695/
  10. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/nickfarr/2160949847/
  11. The current preview release is not the complete solution of the TFS Functionality but still we can use the below productsSource ControlWork Item TrackingAgile Project Management (New in TFS 11)TestingBuild AutomationWe can use the below clients to connect to the TFS Cloud once we are done with the successful registration. The client includingVisual Studio 2010Test Professional 2010Visual Studio 11 ( Not available except MSDN Subscribers(Team Explorer EverywhereMicrosoft Office Integration
  12. Photo credits: Flickr Creative Commonshttp://www.flickr.com/photos/xjrlokix/5097846224/