| On the one hand if this is personal to each individual and if the data feed is entirely private so that only the person interfacing with the agent sees the recommendations, admonishments, and trends...it could be a powerful way to foster more self-improvement. But on the other hand, knowing that another person would wield this with authority over someone else makes it really dystopian. It would be micromanagement to an extreme. People need a concrete goal or specific feature to work on, one that takes time and space to work on. You can't easily or usually create units of measurable work where everything is a story point or a widget. In fact I'd say most of the time the real work isn't like that at all. That's just not how software development works, at least in environments that are conducive to real software engineering. Any EMAI outputs or recommendations that adhere to and respect the reality of actual software engineering will be of limited value to a business head or a scrum master. It'll offer things like how to improve your work flow, or what tools would benefit your work flow. These things don't translate into more story points any time soon, and certainly not within a matter of days... > Using real-time data on each engineer's strengths, past performance, learning curve, and even their preferred working hours, EMAI allocates tasks from the backlog. It uses predictive modeling to optimize for both efficiency and team satisfaction. > End-of-Day Reports: Every team member receives a personalized report detailing their accomplishments, areas of improvement, and resources for further learning. These reports aren't just data-driven and include motivational feedback designed to boost morale and foster continuous learning. If it's allocating tasks this way from a backlog and trying to give you daily reports, this just sounds like something that would be of interest to a ticket farm rather than to a tech company that is really building software. |