Adam Cogan reviews the Tesla Model S

Adam Cogan takes you through the good and the bad of his 2015 Tesla Model S.

List of things to improve:

  1. Profile – Support for more than 10 users
  2. Centre storage as standard
  3. Back seats – Clips to hang shirts
  4. Pre-installed dashcam
  5. Phone mount
  6. Weight driver to select profile
  7. Keep driver statistics
  8. Cameras above front wheels
  9. Physical button to open front trunk (inside and outside)
  10. Sound to confirm the car is locked
  11. Notifications on phone that windows are down
  12. Add Skype app
  13. Add weather app
  14. Add web browser
  15. Add mail app
  16. Introduce app for Windows Phone *irrelevant
  17. Show which profile used which bluetooth device
  18. Improve updating experience

It would be great if Tesla considered adding this feature to its cars.

Time Zone – Change “All Day Appointment” to be an all day appointment

Outlook currenly uses 12 AM to 12 PM for All Day Events. This creates problem when it is for different time zone. A full-day event is a full-day event, no matter what time zone your are in.

It would be useful to use additional time zone feature in outlook to display local time zone without changing time of operating system. Either you can change all day event to local time zone setting.

One best option to handle with this problem is storing all time zone using UTC(Universal Cordinated Time) so that there is no need for any other time settings and appointment can be rendered using local time zone.

Ken Getz says more on this:
Time Zone Disaster – All Outlook Appointments Bite the Dust

How to sell the fact that Scrum does not allow for any time or cost estimates?

Scrum pushes the fact that devs are bad at estimating, and instead of providing methods to help with this process, it asserts that you should simply explain that any estimate will be wrong, so we’re just going to work on the most important stuff 1st, and then when the client runs out of money, we’ll stop. How can this compete against competitors who give a price up front? Is there any guidance on how to sell this?

Give some examples

The scrum guide is very generic, which is great to make it accessible to anyone, but this is at the cost of being specific enough to be very useful.

I would love to see examples of:

  • How a dev team can predict capacity
  • How a Product Owner can predict the end date of a project
  • How a PO defines the value of a Product Backlog Item (PBI)
  • How a team should estimate the size of PBIs