In one team, 3 points might be equivalent to 3 days work. In another it might be 1 day.
In one team, 3 points might be equivalent to 3 days work. In another it might be 1 day.
Not sure when I'll have a chance to use them but seems pretty comprehensive in covering all the basics.
I think that "whatever we do" is doing a lot of heavy lifting here. Some of those "whatevers" will be isomorphic to a frame-level analysis that pulls out structural commonalities, or close enough that it's not a clunky reductionist analogy.
1. RAG your data 2. Magic 3. Agent business logic 4. $$$
where step 2 is very unclear.
Also agent architecture what is it? A basic FSM which in essence is a bunch of business logic/rules with LLM API calls, how do you make this reliable for transactions.
I've yet to see a decent example of a business process replaced which isn't a question answer scenario i.e. call centre type role.
What do you do with the remaining 4 hours and 55 minutes?
The take home test tells me little. I don't know who did the work, how long it took. I know they must really need the work because they gave away 2 hours of free work, that might be a red flag. If they guessed the coding standards we use then we pass them?
If you care about seeing their code ask them for a sample. Some people people github profiles with code on their resume. Use some of the time you have: the 4 hours 55 minutes and check yourself. It will be more representative of their work.