What's your gut reaction to this job posting?

Ok, I wouldn't normally post a job listing, but this one came across my desk this morning and the recruiter was very polite. While you can definitely email me off list for contact info, I am interested in the response from our community as to what your gut reaction is. Technically I do all of this for Assembla (albeit part-time consulting), but our system is largely automated, so there isn't as much project as there is product work to do.

Jobs I have taken that are like this I networked my way to so there was no formal description... I created my own position. Seeing it all listed here was a little daunting and I passed on the position. I didn't think I could go in cold to a company and pull all this off without knowing people first. Even if you are currently employed, what is your gut reaction? Do you think you could pull this off?

Here is the listing:

Responsibilities:
? Responsible for successful completion of online media software development projects on time and within budget
? Manage mixed team of internal developers, third-party vendors and other resources dedicated to media applications
? Familiar with Project Management agile methodologies including Scrum (Scrum is an absolute must), XP and Test Driven Development
? Responsible for maintaining scope, phases, tasks, work breakdown structure, and personnel resources to meet the corporate expectations for project delivery
? Oversee user story backlog, planning phase (requirement and system analysis), design, coding, software build process, QA testing, and system documentation
? Implement effective management controls-tracking and reporting against project plan, budget, and resource utilization
? Responsible for team and inter-department communication
? Responsible for change control of new software features and requests
? Proactively address problems through risk management and contingency planning and present solutions and/or options to executive management
? Consult and take direction from executive management through weekly meetings and reports
? Communicate across multiple organizational levels to effectively identify and solve or escalate problems.

Qualification and requirements:
? Three or more years of experience managing large-scale media application projects through full development life-cycle
? Minimum two years of software engineering with server-side technologies
? In-depth knowledge of web systems and web development
? Demonstrated strength in written and verbal communications
? Entertainment or broadcast industry knowledge
? Highly motivated, hands-on technical leader with proven track record in project management.

Okay, first of all most recruiters at this point in time do not understand Agile and this is not uncommon since they usually get their requirements from the client. That means we need to do more work to educate clients and corporations. We also must take time to educate our recruiters and sales force.

Many experienced Agile practitioners can meet these job expectations that you have shared ? if they have media background or if the client is willing to take a chance on those that have Agile experience but not media experience ? or variations of the above?.

My "thoughts" on your questions:

"Responsible for successful completion of online media software development projects on time and within budget"

On time and on budget does not equal success. Customer satisfaction and ROI equals success.

"Manage mixed team of internal developers, third-party vendors and other resources dedicated to media applications"

Strive towards a team of collaborating generalists but optimize your circumstances.

"Familiar with Project Management agile methodologies including Scrum (Scrum is an absolute must), XP and Test Driven Development"

Scrum and XP are not methodologies but that is great, especially if the employer or client actually support these methods.

"Responsible for maintaining scope, phases, tasks, work breakdown structure, and personnel resources to meet the corporate expectations for project delivery"

Not an usual request - typical project management type of activities - phases will need to be explained further. I would challenge work breakdown structure and change it to product breakdown structure. Project Managers are more servant leader and responsible for removing impediments and championing Agile techniques.

"Oversee user story backlog, planning phase (requirement and system analysis), design, coding, software build process, QA testing, and system documentation"

Oversee might not be the best description - facilitate might be a better word. There should be more explanation about working with the customer/product owner and the team.

"Implement effective management controls-tracking and reporting against project plan, budget, and resource utilization"

Product and Sprint burndowns, daily stand-up, scrum of scrums, velocity and capacity tracking, release plan, testing stats, etc.

"Responsible for team and inter-department communication"

Okay, except it should evolve around servant leadership

"Responsible for change control of new software features and requests"

Change control still exists except it is dealt with in the product backlog and is directed by the customer/client. Change can still be documented in traditional methods if required.

" Proactively address problems through risk management and contingency planning and present solutions and/or options to executive management"

No change - the whole team is involved in this.

"Consult and take direction from executive management through weekly meetings and reports"

You encourage more participation, they should be involved in Sprint planning meetings, Sprint review meetings, product backlog verification and prioritization, involvement as pigs in daily stand-ups, involvement (if needed) in retrospectives, and organization change agents and enforcers.

"Communicate across multiple organizational levels to effectively identify and solve or escalate problems."

Okay, Agile will force this early but this is mostly organizational change. You have to be prepared for that.

Great response Bob!
This posting sounds like they are looking for a project manager to work in a Waterfall environment, but asking for Scrum experience. ??? There is no Work Breakdown Structure in Scrum, or change control, or overseeing those phases mentioned (planning phase, design, coding, software build process, QA testing, and system documentation-they all happen within a sprint, you don't have separate them into individual phases). I get a completely mixed message from this post...