Practical Programming
Traditional vs. Agile
The System Development Process Requirements Analysis System Design Program Design Program Implementation Testing Delivery ...
<ul><li>Struggles of Traditional Programmers: </li></ul><ul><li>Estimating overall cost </li></ul><ul><li>Estimating preci...
Murphy's Law: Things will go wrong in any given situation, if you give them a chance.
Programming Rule #1: You will make mistakes.
Programming Rule #2: Make sure you can correct mistakes.
<ul><li>Agile Programming comes in different forms and may take on different names: </li></ul><ul><li>Extreme Programming ...
<ul><li>The Need to be Agile </li></ul><ul><li>Rapidly changing requirements </li></ul><ul><li>Changing environment </li><...
 
Scrum Scrum is an agile process for developing software. With Scrum, projects progress via a series of month-long iteratio...
Product Backlog The Product Backlog is the master list of all functionality desired in the product. When a project is init...
Product Owner The Product Owner is typically someone from a Marketing role or a key user in internal development.He commit...
The Scrum Team Scrum teams do not include any of the traditional software engineering roles such as programmer, designer, ...
The Sprint Begins The Sprint Planning Meeting is attended by the Product Owner, Scrum Master, the entire Scrum Team, and a...
During the sprint planning meeting the product owner describes the highest priority features to the team. The team asks en...
Sprint Backlog The sprint backlog is the list of tasks that the Scrum team is committing that they will complete in the cu...
Ham and Eggs
<ul><li>Pigs  are people  committed  to the project. They speak and make decisions. </li></ul><ul><li>Chickens  are people...
<ul><li>The Daily Scrum </li></ul><ul><li>Each day during the sprint, the team conducts a brief daily meeting. Team member...
<ul><li>My false teeth broke and I need a new one today. </li></ul><ul><li>I still haven't gotten the software I ordered a...
Sprint Review Meeting Typically, this is a demo. It should be a natural result of the sprint. Participants in the sprint r...
 
Extreme Programming Continuous integration, relentless testing. Smalltalk: &quot;Code a little, test a little&quot; Coding...
User needs are met.
Performance testing Ex. load testing Usability testing - real users, real environment
&quot;Failure to meet usability criteria is just as big a bug as dividing by zero.&quot;
D - R - Y -  Yourself Don't Repeat
Test thoroughly. Introduce bugs on purpose. There is no perfect program, and you will never catch all the possible errors....
Documentation The palest ink is better than the best memory.  - Chinese Proverb
<ul><li>Comments in code – describe  why  something is done </li></ul><ul><li>Variable names </li></ul><ul><li>Function na...
Conclusion The success of a project is measured by how well it meets the expectations of its users. Never lose sight of th...
Eversun Software Philippines Corporation 5 th  Floor, Djongjin Bldg. Valeria Street, Iloilo City Web:  http://www.agentsof...
Upcoming SlideShare
Loading in...5
×

Practical Programming It Awareness Advocacy

496

Published on

A short presentation prepared by my colleague, Rex Jason Alobba, for an IT week lecture-forum.

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
496
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Practical Programming It Awareness Advocacy"

  1. 1. Practical Programming
  2. 2. Traditional vs. Agile
  3. 3. The System Development Process Requirements Analysis System Design Program Design Program Implementation Testing Delivery Maintenance What is the problem? What is the solution? What are the mechanisms that best implement the solution? How is the solution constructed? Is the problem solved? Can the customer use the solution? Are enhancements needed?
  4. 4. <ul><li>Struggles of Traditional Programmers: </li></ul><ul><li>Estimating overall cost </li></ul><ul><li>Estimating precise project timelines </li></ul><ul><li>Unexpected corporate changes </li></ul>
  5. 5. Murphy's Law: Things will go wrong in any given situation, if you give them a chance.
  6. 6. Programming Rule #1: You will make mistakes.
  7. 7. Programming Rule #2: Make sure you can correct mistakes.
  8. 8. <ul><li>Agile Programming comes in different forms and may take on different names: </li></ul><ul><li>Extreme Programming </li></ul><ul><li>Scrum </li></ul><ul><li>Pragmatic Programming </li></ul><ul><li>But the purpose stays the same. </li></ul>
  9. 9. <ul><li>The Need to be Agile </li></ul><ul><li>Rapidly changing requirements </li></ul><ul><li>Changing environment </li></ul><ul><li>Changing laws </li></ul><ul><li>Changing people </li></ul><ul><li>Mistakes on the initial planning stage </li></ul>
  10. 11. Scrum Scrum is an agile process for developing software. With Scrum, projects progress via a series of month-long iterations called sprints . Scrum is ideally suited for projects with rapidly changing or highly emergent requirements.
  11. 12. Product Backlog The Product Backlog is the master list of all functionality desired in the product. When a project is initiated there is no comprehensive, time-consuming effort to write down all foreseeable tasks or requirements.
  12. 13. Product Owner The Product Owner is typically someone from a Marketing role or a key user in internal development.He commits that he or she will not throw new requirements at the team during the sprint. Requirements are allowed to change (and change is encouraged) but only outside the sprint .
  13. 14. The Scrum Team Scrum teams do not include any of the traditional software engineering roles such as programmer, designer, tester, or architect. Everyone on the project works together to complete the set of work they have collectively committed to complete within a sprint.
  14. 15. The Sprint Begins The Sprint Planning Meeting is attended by the Product Owner, Scrum Master, the entire Scrum Team, and any interested and appropriate management or customer representatives.
  15. 16. During the sprint planning meeting the product owner describes the highest priority features to the team. The team asks enough questions during this meeting so that they can go off after the meeting and determine which tasks they will move from the product backlog to the sprint backlog.
  16. 17. Sprint Backlog The sprint backlog is the list of tasks that the Scrum team is committing that they will complete in the current sprint.
  17. 18. Ham and Eggs
  18. 19. <ul><li>Pigs are people committed to the project. They speak and make decisions. </li></ul><ul><li>Chickens are people involved in the project. They are seen but not heard. </li></ul>
  19. 20. <ul><li>The Daily Scrum </li></ul><ul><li>Each day during the sprint, the team conducts a brief daily meeting. Team members will meet on a daily basis and ask each other three questions: </li></ul><ul><ul><li>What did you do yesterday? </li></ul></ul><ul><ul><li>What will you do today? </li></ul></ul><ul><ul><li>Are there any impediments in your way? </li></ul></ul>
  20. 21. <ul><li>My false teeth broke and I need a new one today. </li></ul><ul><li>I still haven't gotten the software I ordered a month ago. </li></ul><ul><li>I'm struggling to learn PHP and would like to pair with someone on it. </li></ul><ul><li>I can't get the vendor's tech support group to call me back. </li></ul><ul><li>Our new contractor can't start because no one is here to sign her contract. </li></ul><ul><li>I can't get the HR group to give me any time and I need to meet with them. </li></ul><ul><li>The department VP has asked me to work on something else &quot;for a day or two.&quot; </li></ul>Things that may come up:
  21. 22. Sprint Review Meeting Typically, this is a demo. It should be a natural result of the sprint. Participants in the sprint review typically include the Product Owner, the Scrum team, the ScrumMaster, management, customers, and engineers from other projects.
  22. 24. Extreme Programming Continuous integration, relentless testing. Smalltalk: &quot;Code a little, test a little&quot; Coding ain't done 'til all the tests run.
  23. 25. User needs are met.
  24. 26. Performance testing Ex. load testing Usability testing - real users, real environment
  25. 27. &quot;Failure to meet usability criteria is just as big a bug as dividing by zero.&quot;
  26. 28. D - R - Y - Yourself Don't Repeat
  27. 29. Test thoroughly. Introduce bugs on purpose. There is no perfect program, and you will never catch all the possible errors. Let the first time you find a bug be the last time you find that bug.
  28. 30. Documentation The palest ink is better than the best memory. - Chinese Proverb
  29. 31. <ul><li>Comments in code – describe why something is done </li></ul><ul><li>Variable names </li></ul><ul><li>Function names - underscores or intercap notations </li></ul><ul><li>ex. save_file_now() </li></ul><ul><li>saveFileNow()‏ </li></ul>
  30. 32. Conclusion The success of a project is measured by how well it meets the expectations of its users. Never lose sight of the business problems your application is intended to solve. Give the users a bit more than they were expecting.
  31. 33. Eversun Software Philippines Corporation 5 th Floor, Djongjin Bldg. Valeria Street, Iloilo City Web: http://www.agentsofvalue.com My email: rex.a@agentsofvalue.com Our Company Phone: 338-3106, look for Mia

×