Mimosa Story (incomplete version)

652 views

Published on

My FYP Presentation Slides in a story-telling fashion (removed a number of slides due to confidentiality issue)

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

  • Be the first to like this

No Downloads
Views
Total views
652
On SlideShare
0
From Embeds
0
Number of Embeds
120
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Add photos. FATED.
  • The client is impressed with our prototype so…
  • Yes, we kept to our promise and managed to complete Phase 1 in less than 2 weeks. So it was time for us to deploy our application!
  • However, our initial excitement turned into frustration when we could not run our application.We tried to trace our deployment steps to check if we made some careless mistakes when deploying but that was not the cause of the problem.We also tried to run the code from the surface machine but it could not compile. That was when we suspect that the .NET framework on the surface machine was probably not latest version. So we did a windows update and everything could run smoothly after that.Something we found out when we were trying to do connect to internet to do windows update was that the surface machine has no access to the bank’s network! This has implications on several functionalities such as email, print and file transfer which requires access to the bank’s network. In the later part of our presentation, wahlin will talk about how we manage and work within this constraint.
  • This incident showed us that our deployment was not planned properly. In fact, there wasn’t even a plan! We were disorganized and did not know what to do when a problem arise.From this, we learnt that we need to plan our deployment to make full use of the little chance we had to deploy our application. We should also try to expect the unexpected because problems are bound to happen.Even so, we felt that we needed someone to oversee the deployment. Hence, we appointed Firdaus as our deployment manager who has to know all the deployment and configuration steps by heart. He also needs to prepare the detailed deployment steps clearly stating the schedule and who should do what and bring all the necessary files for deployment.To sum up, our lessons learnt can be encapsulated in this quote: he who fails to plan, plans to fail.
  • Firstly, consider the business context. Initially we did not take into account that this application is for the private banking sector, which is why we kept on thinking about how to make the application cool and fanciful when what the client wanted was something professional. Hence, we had to align our application to suit the private bank’s brand image.Secondly, consider the end users, which in our case are the private bankers and their clients, who are affluent, middle age and might not be technologically savvy. We have to bear in mind the end users to tailor our application to suit them.Thirdly, consider the client feedback. It is important to pay attention to their feedback in order to build an application which the client wants and needs, and not just what we like.
  • After meeting the bankers, it was time to meet our supervisor!Is he an angel or a devil? We did not know but…
  • So, How will the meeting turn out?
  • This part should be more of like.. How we viewed supervisor’s meeting as a chore?Soccer team analogy
  • Need to elaborate why he asked us this question? I think he asked this because phase 2 seems uselessalr…and phase 1 got new requirement (ticker)????What should the main focus of our project be?
  • KS: After this point, we already know how to work effectively (normal standard stable process & good practices formed. There was a system in place.) – regular meetings, agile etc.
  • We decided to have equal focus on both – hence we split the team into 2We’re still a team – meet and discuss as a team, gave valuable feedback to one anotherKS: We need to have solid project mgmt process to cope  regular client meeting etc.
  • KS: Put it at the “impressive” slide. Or before “meeting the supervisor” slide… because we’re already getting so much feedback.
  • KS:Being stressed led us to prepare the slides in this way, which is good actually.Talk about our feelings about meeting supervisor. [link to previous slide]What did u get out of the meeting? Another viewpoint. Additional ideas. Advice. Client & supervisor has different views/suggestions  how to resolve? Wanna mention?Why did we have 2 back to back meetings? No time to incorporate feedback?
  • We have worked so hard. It was time to prove our worth! First UAT, here we go…
  • To change this to a nicer question.
  • We will show a list of our functionalities during demoKS: put special thanks in surface tableKS: Come up with a demo which prompts audience (which stock would u like to view?)
  • Mimosa Story (incomplete version)

    1. 1. A journey intothe Multi-touch jungle<br />GAN Kah Hwee - Muhammad Firdaus Bin OSMAN - NGU Wah Lin - SU Mon Kywe - Tessie SZETHO Peixin - TRAN Van Minh Phuc<br />
    2. 2. Episode 1Love at First Touch<br />
    3. 3. Why Multi-touch?<br />One year ago…<br />Love at First SIGHT!<br />Love at First TOUCH!<br />
    4. 4. Mimosa comes together<br />
    5. 5. Nothing comes without sacrifice…<br />even freedom is not free<br />Install Windows Vista<br />Need to acquire external screens<br />one member even went back to Malaysia and brought over her monitor<br />Meeting at night (until last train and bus!) and weekends.<br />Internship compromise<br />Take leave for project deployment<br />
    6. 6. is impossible really impossible?<br />
    7. 7. Episode 2The Journey Begins<br />
    8. 8. Peer-to-Peer Learning<br />expert system<br />Good Practice<br />Something very impressive:<br />Firdaus: 38 slides<br />Phuc: Hello Kitty slides<br />
    9. 9. Tada! Our 1st Prototype<br />
    10. 10. “Impressive!”<br />Why not…<br />
    11. 11. Emergence of Phase 1<br />Additional scope<br />Project Scope<br />New requirement? Yes.<br />But it’s ok! That’s not too much.<br />We promised to finish in 2 weeks.<br />
    12. 12. were we able to keep our promise?<br />
    13. 13. Episode 3First Date<br />
    14. 14. First deployment<br />Yes, we managed to complete Phase 1 in less than 2 weeks!<br />Time to deploy!<br />
    15. 15. Chaos!<br />Problem: We could not run the application<br />Analyzing the problem:<br />Did we deploy correctly?<br />Is the code buggy?<br />Solution: Windows Updates<br />Constraint: No access to network<br />
    16. 16. Mistakes and Remedies<br />Mistakes<br />Deployment was not planned properly<br />Disorganized<br />Remedies<br />Plan our deployment<br />(try to) expect the unexpected<br />Appoint a deployment manager (Firdaus)<br />Know the deployment steps by heart<br />Prepare detailed deployment steps<br />Bring all the necessary files<br />Lessons learnt<br />“He who fails to plan, plans to fail”<br />
    17. 17. Important considerations<br />Lessons learnt<br />Business context<br />Private banking sector<br />End users<br />Private bankers<br />Private bank clients<br />Client feedback<br />What the client wants and needs<br />
    18. 18. Time to meet our supervisor<br />or<br />?<br />
    19. 19. how will the meeting turn out?<br />
    20. 20. Episode 4Turbulent Times<br />Lost in the dense jungle<br />
    21. 21. 1st Supervisor Meeting<br />Lessons learnt<br />Met our supervisor on 20th July<br />After almost 3 months into the project<br />About 35% of the project completed<br />Supervisor’s feedback<br />Multi-touch must add business value<br />Computer-like design<br />It seems like our supervisor is hard to please and has high expectations<br />
    22. 22. In response to the change in requirements -<br />“aren’t you worried?”<br />- Kevin Steppe<br />What should the main focus of our project be?<br />
    23. 23. Episode 5Blood, Sweat and Tears<br />When the going gets tough, the tough get going!<br />
    24. 24. Coping with the changes<br />Equal focus on those phase 1 and 2<br />Split the team into 2 sub teams<br />Ticker Team<br />Work on Phase 1<br />Firdaus, Phuc, Su Mon<br />Explorer Team<br />Work on Phase 2<br />Kah Hwee, Ngu Wah, Tessie<br />Work on Phase 1 & 2 in parallel<br />Public Folder for Phase 2<br />We are still a team!<br />
    25. 25. Regular Meeting with Clients <br />Update clients on our progress<br />Verify that we are on the right track<br />Get feedback from clients<br />Clarify the requirements<br />Good Practice<br />
    26. 26. Weekly Meeting with Supervisor<br />Good Practice<br /><ul><li>Prepare slides for supervisor meeting
    27. 27. What we planned to do last week
    28. 28. What we did
    29. 29. What we plan to do next week
    30. 30. A good way to keep track of our progress
    31. 31. Will use this method in future
    32. 32. Good stress!</li></li></ul><li>Agile methodology<br />Good Practice<br />From Client & Supervisor<br />
    33. 33. Updates on project progress<br />Phase 1 Enhancement<br />
    34. 34. Updates on project progress<br />Phase 2<br />
    35. 35. Time to prove our worth!<br />
    36. 36. 1st UAT<br />Eager<br />Confident<br />Prepared<br />Happy<br />
    37. 37. 1st UAT<br />Life is unexpected...<br />And the truly unexpected, well, can never be expected<br />
    38. 38. Episode 6End of the World<br />
    39. 39. End of project?<br />
    40. 40. Life moves on<br />“Prepare for the worst (is there any worse situation anyway), and hope for the best”<br />
    41. 41. Still sad…<br />We prayed day and night for a miracle to happen.<br />Will our prayer be answered?<br />
    42. 42. Episode 7Miracles do happen!<br />when you believe<br />
    43. 43. So what are we waiting for?<br />

    ×