Skip to main content
37 events
when toggle format what by license comment
Jun 4, 2019 at 15:01 history tweeted twitter.com/StackGameDev/status/1135924427491872769
May 18, 2019 at 16:32 comment added Jasper People are bad at estimating how much time they need for something as well how much time they can actually be productive in a given period. Therefore, a manager should be used to multiplying estimates by a relatively large number to get the real expected amount of time.
May 18, 2019 at 16:22 answer added Cooper Buckingham timeline score: 2
S May 18, 2019 at 12:49 history suggested user40973 CC BY-SA 4.0
removed an edit containing a comment to answers
May 18, 2019 at 11:38 comment added TomTom "we're working on a big project" - no. This is a small proejct because it seems to ahve 2 only developers. Large projects are mutliple SCRUM teams of 5-7 productive people each, plus testers, busines analysists etc.
May 18, 2019 at 0:04 answer added bokan timeline score: 2
May 16, 2019 at 22:06 review Suggested edits
S May 18, 2019 at 12:49
May 16, 2019 at 20:40 comment added Dan Mašek Just curious -- given that it's 2 (or 3 people, not sure what your exact involvement is) people, lead level, working on what appears relatively independent tasks, what's the benefit of having them sitting in the office strictly between 9am and 5pm everyday. We never needed anything so draconian with significantly larger teams in a company orders of magnitudes larger. Trust your people, let them self-organize. This is not a factory job standing at a production line cranking out the same thing over and over.
May 16, 2019 at 19:41 history edited user128176 CC BY-SA 4.0
added 216 characters in body
May 16, 2019 at 19:40 comment added user128176 @lucasgcb So, we're at the very start of the process in developing the game, and we have some tight deadlines as well. But, what I've really tried to plan for (fully realising they'll readjust and change) are some of the initial sprints and features we might like to build out during those.
May 16, 2019 at 19:38 vote accept CommunityBot
May 16, 2019 at 19:38 vote accept CommunityBot
May 16, 2019 at 19:38
May 16, 2019 at 19:38 vote accept CommunityBot
May 16, 2019 at 19:38
May 16, 2019 at 19:38 vote accept CommunityBot
May 16, 2019 at 19:38
May 16, 2019 at 17:43 answer added StackOverthrow timeline score: 6
May 16, 2019 at 17:27 comment added bob It sounds like you may be holding onto waterfall thinking while trying to lead an Agile team. See my answer below for my recommendations.
May 16, 2019 at 17:24 answer added bob timeline score: 10
May 16, 2019 at 17:16 comment added bob How late were they? What kind of commute do they have--how variable is the travel time due to traffic? How did you communicate the policy of coming in at 9? Did you communicate it as "You're expected to start work at 9am" or "We generally try to start work at 9am"? Those details make a big difference between having employees who aren't respecting a policy, employees who may just be getting caught in traffic, a boss who needs to lighten up (e.g. if they're less than 5 min late), and a boss who hasn't communicated expectations clearly.
May 16, 2019 at 14:30 answer added ribs2spare timeline score: 21
May 16, 2019 at 12:39 history edited Vaillancourt CC BY-SA 4.0
additional info from the comments
May 16, 2019 at 11:57 comment added MechMK1 I can tell you from personal experience that giving estimates is hard. Very hard. You just can't know what will happen in the future, how long a certain task will take. And yes, I need coffee breaks too. The brain is like a muscle and overexercising it will yield diminishing returns. From what I could see, it seems you have too high of expectations what your employees can do per day. Forcing them to comply with your expectations will burn them out, as was seen with BioWare and others.
May 16, 2019 at 11:17 answer added Thomas timeline score: 9
May 16, 2019 at 9:15 comment added Aaron F Ever heard the saying "You can have it on time, on budget, on spec. Pick two." ? Well you've apparently chosen time and budget. Guess what's going to happen to your project.
May 16, 2019 at 8:42 comment added lucasgcb If the OP did set up a roadmap with deadlines for each and every point then yeah that's nothing Agile. Is this really the case, OP?
May 16, 2019 at 8:30 comment added Jörg W Mittag @lucasgcb: But those deadlines are short (typically one or two weeks), re-evaluated every sprint, and set by the team. None of that is the case here, as the OP wrote, he set out the entire roadmap and the deadlines before the project even started. Agile is about continuous feedback and adjusting the process based on that feedback.
May 16, 2019 at 8:27 comment added lucasgcb @JörgWMittag More or less on the deadlines; Sprints in Scrum within Agile can be interpreted as having deadlines.
May 16, 2019 at 8:06 answer added lucasgcb timeline score: 5
May 16, 2019 at 7:48 comment added JollyJoker For the artist refusing other work, isn't this just a matter of priorities? Of course extra work will affect deadlines, but isn't it your job to prioritize?
May 16, 2019 at 7:27 comment added Jörg W Mittag Setting down a project roadmap, including deadlines, in advance, is the exact opposite of Agile project management.
May 16, 2019 at 6:06 answer added dcruise546 timeline score: 16
May 16, 2019 at 0:41 history became hot network question
May 16, 2019 at 0:40 answer added Coldsteel48 timeline score: 18
May 15, 2019 at 23:07 answer added DMGregory timeline score: 87
May 15, 2019 at 21:45 answer added Jasper W timeline score: -1
May 15, 2019 at 19:40 review Close votes
May 20, 2019 at 3:05
May 15, 2019 at 19:17 comment added Vaillancourt Comments should be used to improve the question. Please use the "Your Answer" box below to post an answer. Please avoid repeating what has already been written.
May 15, 2019 at 19:06 history asked user128176 CC BY-SA 4.0