Managing Phone Dev ProjectsJohn McKerrell
Introduction - About Me
My EducationReceived a 2.1 in Computer Science fromUniversity of LeedsWas taught Pascal in 1st year, C++ 2nd & 3rdFinal ye...
My ExperienceWorked in Manchester on the official website forthe Barclaycard PremiershipAlso other bespoke Content Managem...
My ExperienceWent on to work for Multimap.com building theirJavaScript mapping APIWorked for Microsoft for six months afte...
FreelanceHave been developing for iOS for over 2 yearsHave had 50 apps available on the iOS app storeRecently launched 18 ...
Brainstorming, Ideas
Brainstorm FeaturesPost-it notes are a greatway to brainstorm  Write down lots of ideas  Collect related ideas  into group...
Brainstorm FeaturesMind maps are a great way to collect and organiseideas  Can use online tools such as mindmeister.com to...
Brainstorm Features
Ideas can come at any timeTake time out awayfrom the computerGive yourself as muchtime as possible tothink things through ...
Designing your app
DesignCollect together thoughts from brainstormingPrioritiseBuild up a picture of what youre going to build
DesignAlways stop and think before doing any largechunk of development
DesignBuild up a high level view of the systemIdentify ways to split work into modules  Allows work to be split between pe...
Prioritise
Lists!Task list gives you something simple to follow asyou work through the projectIndividual tasks become much less about...
The Trac ProjectProject management and issue tracking system.Fine-grained control of issue managementIntegrated wikiCan ho...
GithubFree hosting for Open Source SoftwareProvides basic issue tracking systemAlso allows code check-ins to resolve issue...
Lots more optionshttp://tadalist.com/http://www.rememberthemilk.com/iCalOutlookGoogle Docsetc!
Managing your Code
Source ControlGit  Simple to use on your own, doesn’t require a  central repository  Better support for branching  Great f...
Source ControlSubversion Requires a central repository Can be simpler to understand than Git Been around for longer than Git
Keep your source treetidyYour code should be modular so arrange it insubdirectoriesRoot directory of your project should u...
CommentingReally is importantEspecially with particularly fiddly code, such as acomplex algorithmAlthough... when using id...
CommentingBest thing with a difficult function or method isto write it out in English or “pseudo-code” first toget the fun...
Testing
Test-drivendevelopmentGenerally written as unit testsWrite the tests before you write the codeIn a similar way to lists, m...
Documentation driventestingIf you document what the system will do wellenough, the functionality can be tested by simplygo...
Test PlansFor entire apps or website, full user testing isneeded to be sure of qualityCreating a detailed and complete tes...
Found a bug?Add the bug to your issue trackerIf possible add unit tests that find the bugAdd checks to the test plan that ...
Conclusions
Allow yourself as muchtime as possible
Spend time working outwhat you’re going to do
Use good tools to aidyour progress
Be meticulous andorganised
Thank youJohn McKerrell - http://johnmckerrell.com/
Managing Phone Dev Projects
Upcoming SlideShare
Loading in...5
×

Managing Phone Dev Projects

394

Published on

A short talk I gave to give some students at Salford University pointers on managing their projects.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
394
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Managing Phone Dev Projects

    1. 1. Managing Phone Dev ProjectsJohn McKerrell
    2. 2. Introduction - About Me
    3. 3. My EducationReceived a 2.1 in Computer Science fromUniversity of LeedsWas taught Pascal in 1st year, C++ 2nd & 3rdFinal year project was in “Classic” ASP with SQLServer
    4. 4. My ExperienceWorked in Manchester on the official website forthe Barclaycard PremiershipAlso other bespoke Content ManagementSystems built on LAMP (Linux, Apache, MySQL,PHP)
    5. 5. My ExperienceWent on to work for Multimap.com building theirJavaScript mapping APIWorked for Microsoft for six months after theybought Multimap
    6. 6. FreelanceHave been developing for iOS for over 2 yearsHave had 50 apps available on the iOS app storeRecently launched 18 apps on Android Market Place
    7. 7. Brainstorming, Ideas
    8. 8. Brainstorm FeaturesPost-it notes are a greatway to brainstorm Write down lots of ideas Collect related ideas into groupsAlso good for“User Stories” “slim and high-level requirements” HTTP://WWW.FLICKR.COM/PHOTOS/YANDLE/2055035926/
    9. 9. Brainstorm FeaturesMind maps are a great way to collect and organiseideas Can use online tools such as mindmeister.com to allow shared use within a group Also offline tools such as Freemind are available
    10. 10. Brainstorm Features
    11. 11. Ideas can come at any timeTake time out awayfrom the computerGive yourself as muchtime as possible tothink things through HTTP://WWW.FLICKR.COM/PHOTOS/CPOYATOS/4374856699/
    12. 12. Designing your app
    13. 13. DesignCollect together thoughts from brainstormingPrioritiseBuild up a picture of what youre going to build
    14. 14. DesignAlways stop and think before doing any largechunk of development
    15. 15. DesignBuild up a high level view of the systemIdentify ways to split work into modules Allows work to be split between people Helps with re-useLook for existing code that can be used, OpenSource libraries etc.
    16. 16. Prioritise
    17. 17. Lists!Task list gives you something simple to follow asyou work through the projectIndividual tasks become much less about the bigpicture and more focussed on the task at hand
    18. 18. The Trac ProjectProject management and issue tracking system.Fine-grained control of issue managementIntegrated wikiCan hook into source control to link checked-incode to resolved bugsFree Open Source Software HTTP://TRAC.EDGEWALL.ORG/
    19. 19. GithubFree hosting for Open Source SoftwareProvides basic issue tracking systemAlso allows code check-ins to resolve issues HTTPS://GITHUB.COM/
    20. 20. Lots more optionshttp://tadalist.com/http://www.rememberthemilk.com/iCalOutlookGoogle Docsetc!
    21. 21. Managing your Code
    22. 22. Source ControlGit Simple to use on your own, doesn’t require a central repository Better support for branching Great for distributed teams
    23. 23. Source ControlSubversion Requires a central repository Can be simpler to understand than Git Been around for longer than Git
    24. 24. Keep your source treetidyYour code should be modular so arrange it insubdirectoriesRoot directory of your project should usuallyhave as little as possibleSeparate modules can even be placed inseparate source control repositories
    25. 25. CommentingReally is importantEspecially with particularly fiddly code, such as acomplex algorithmAlthough... when using identifiers with sensiblenames, commenting can be reduced
    26. 26. CommentingBest thing with a difficult function or method isto write it out in English or “pseudo-code” first toget the functionality clear in your headThen go through the function again, filling in thegaps between comments with working code
    27. 27. Testing
    28. 28. Test-drivendevelopmentGenerally written as unit testsWrite the tests before you write the codeIn a similar way to lists, minimises the “thinking”you have to doWorks best with self contained modules orspecific algorithms
    29. 29. Documentation driventestingIf you document what the system will do wellenough, the functionality can be tested by simplygoing through the design and confirming thatfeatures work as expected
    30. 30. Test PlansFor entire apps or website, full user testing isneeded to be sure of qualityCreating a detailed and complete test planensures testing is consistent
    31. 31. Found a bug?Add the bug to your issue trackerIf possible add unit tests that find the bugAdd checks to the test plan that look out for thebug in the future
    32. 32. Conclusions
    33. 33. Allow yourself as muchtime as possible
    34. 34. Spend time working outwhat you’re going to do
    35. 35. Use good tools to aidyour progress
    36. 36. Be meticulous andorganised
    37. 37. Thank youJohn McKerrell - http://johnmckerrell.com/
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×