Remove Article Remove CTO Hire Remove Finance Remove Software Developers
article thumbnail

How to write an executive summary stakeholders will love

Planio

The budget and scope remain on track, but there are risks to the project’s software development resources following a resignation. Problem: Following a resignation, Beemax has no software development resources with the skills and expertise to progress the project. 60,000) from 1st January. permanent market value.

article thumbnail

What does the Scrum Master do all day?

Scrum.org

Juergen is our CTO). Daniel: You and your German time. As time hits 3:30 pm, Ahmed opens the door and enters the room. You made it on time. A lot of times people who asked this question cannot see any tangible work done by the Scrum Master. We apply the same thinking towards creative work like software development.

SCRUM 193
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

How to identify stakeholders? (+Identification Cheatsheet)

PM Basics

This article explores how you can identify stakeholders within your project. You can now think about ways to negate the potential threat they bring, perhaps by contracting the lunch preparation work to them instead. You can consider communicating via email, phone calls, interviews, or conducting brainstorming sessions.

article thumbnail

Risk Management Resources

Herding Cats

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Project Risk Management: Lessons Learned from Software Development Environment,” Y. Recent trends of Risk Management in Software Development: An Analysis,” Raghavi Bhujang and V.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. 255, April 2010. 920, November 2004. Kwak and J.