Add Callouts to Bootstrap

These informational callouts are littered throughout the online Bootstrap documentation:

Bootstrap Callout

Figure: This is a nicely designed informational callout

They look great, and being used in the Bootstrap documentation I assumed they were part of Bootstrap as well. Unfortunately, they are not.

Please add these to Bootstrap as .callout, with the same contextual options as usual (.callout-default, .callout-primary, .callout-info, etc…)

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