◆ Microsoft Azure

Manage projects with Azure DevOps

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGet the 'Project Phoenix' development board ready for the sprint review on Friday. Make sure…+
Get the 'Project Phoenix' development board ready for the sprint review on Friday. Make sure the 'Backend API' team's tasks are all moved to 'Done' if they've been completed and that the burndown chart reflects the current state for the leadership demo.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore the Project Phoenix sprint review on Friday, I need to make sure the board tells a clear…+
Before the Project Phoenix sprint review on Friday, I need to make sure the board tells a clear story for leadership. Organize the 'Backend API' team's work items so the progress is obvious, highlight any blockers they're still facing, and ensure the overall sprint velocity is easy to grasp.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'Project Phoenix' sprint review is Friday, and the lead developer just told me a critical…+
The 'Project Phoenix' sprint review is Friday, and the lead developer just told me a critical 'Backend API' task is stuck with a vendor. I'm afraid to show an incomplete burndown to the VP, but I also can't just mark it done. What's the best way to represent this without causing a panic or looking like we're hiding something?
The 'Project Phoenix' sprint review is Friday, and the lead developer just told me a critical 'Backend API' task is stuck with a vendor and won't be done. I'm afraid to show an incomplete burndown to the VP, but I also can't just mark it done. What's the best way to represent this without causing a panic or looking like we're hiding something? I need to know how to update the board to reflect this external dependency accurately.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur sprint reviews often involve last-minute scrambling to update development boards, making us…+
Our sprint reviews often involve last-minute scrambling to update Azure DevOps boards, making us look unprepared.
Our sprint reviews often involve last-minute scrambling to update development boards, making us look unprepared and wasting valuable leadership time. We keep losing credibility because the board doesn't reflect reality until minutes before the meeting. What habit should I change to ensure the board is always a true, real-time reflection of our work, even when external blockers hit?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Microsoft Azure's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.