@Berthavlix matches my wife and my approach completely.
Tbh they mostly want the superficial answer without us acting like embarrassed teenagers.
They are content with simple answers and ask more when they want. it takes time for them to process things.
Now they're bringing a lot home from school and asking sometimes. Sometimes we ask them things, and if they know what it means.
But it's early days. they're only 7 & 8. a little early for the 1 yr old to join the fun yet ;)
@Moke oh, that's unfortunate. We have similar issues, but each team decides how to structure their work. Some scrum, our team is doing Kanban. There are still some high level estimating, but slowly moving away from big projects. Most projects are now 2-6 weeks. And more and more work is just "on demand" without projects.
Still have a few monster projects though.
But overall fewer meetings for the teams.
@Moke I'm curious as to how much value you are getting from the planning meeting?
You say that you have approx 2 weeks of development work, but that there isn't time for developing?
I'm confused if that 1 hour planning meeting is what's holding yo back form 2 weeks of work? Perhaps also other meetings that you need to attend during those 2 weeks?
All exceptions are not errors. When an endpoint throws an error that may be some inconvenience from the standpoint of your application / service. But a major/fatal error on their side.
Yea! got a little help from Luggage, and we're off to a flying start.
Also no dragons, yet.
Abstract re-submitted for feedback / approval :)
@thor one of the themes that I hear coming up again and again. Is that the value may not be in the hard work itself, but the habit of showing up.
No guarantees that you'll get that chance meeting, but you're increasing the odds greatly.
I think Scott Adams (creator of Dilbert) wrote it in his book. "How to fail at almost everything and still in big"