Software Engineering and Project Management AdHoc Stories

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    2 Favorites

    Software Engineering and Project Management AdHoc Stories - Presentation Transcript

    1. Software Engineering and Project Management Ad Hoc Stories Mohammed S. Makhlouf – IS Department,4 th year
    2. Our Key Witnesses
      • Fredrick P. Brooks
      • Steve Jobs
      • Sarah Winchester
      • Jack Welch
      • Jacob Nielsen
    3. Lack of planning
      • Winchester Mystery House
    4. Lack of planning
      • Planning is some how a design problem,
      • And
      • “ Design is not just what it looks like and feels like. Design is how it works.”
      • Steve Jobs
    5. Projects usually become late
      • Even if your estimates are so accurate you’re only half done.
      • Projects do get late for one reason or another so hustle hard.
      • Never Add man power to late projects.
      • They only get later !
      • Fredrick P. Brooks
    6. Communication
      • Tower of Babel
      • One big Failure … in Italian it is a fiasco
    7. Methodologies and Details
      • “ Too Often we measure everything and understand nothing.”
      • Jack Welch
      • Time and Attention are Finite!
    8. Methodology
    9. Methodology
    10.  
    11. Cut Features Be realistic about what you really need and what is actually usable.
    12.  
    13. Use it or just try it
      • “ Clear content, simple navigation, and answers to customer questions have the biggest impact on business value. Advanced technology matters much less.”
      • “ Progressive disclosure defers advanced or rarely used features to a secondary screen, making applications easier to learn and less error-prone.”
      • Jacob Nielsen
    14. Code and Documentation
      • Should be fully related and not just a heap of papers.
    15. So what to do
      • For every complex problem there is a solution that is simple, neat and wrong.
      • Fail Fast.
      • Iterate.
      • Explore.
      • This isn’t construction or rocket science.
    16. Insanity
      • The definition of insanity is doing the same thing over and over again and expecting different results.
      • So please don’t repeat these age old problems
      • Thank you, thank you, thank you
      • You are all far too kind

    + msmakhloufmsmakhlouf, 2 years ago

    custom

    827 views, 2 favs, 2 embeds more stats

    I gave this talk on the 3rd year workshop on projec more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 827
      • 784 on SlideShare
      • 43 from embeds
    • Comments 0
    • Favorites 2
    • Downloads 41
    Most viewed embeds
    • 31 views on http://forum.fcicafe.com
    • 12 views on http://jjmak.com

    more

    All embeds
    • 31 views on http://forum.fcicafe.com
    • 12 views on http://jjmak.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories