I am a successful Senior Development Manager with expertise in project life cycles, planning, executing, controlling, closing projects and delivering business innovation and value, thus insuring that my Developers deliver beyond the expectations of stakeholders.

I have developed a wide range of techniques and skills whilst employed with Large and Medium institutions. In particular;

• Introducing simple but key SDLC governance practices
• Conducting regular appraisals and mentoring, Introducing training and self improvement to members
• Managing resources third parties – RFP through development and delivery. Matrix and direct
• Experience with a multiple technologies including; BizTalk, Web Services, dot Net, Oracle and SQL Hands on understanding of PM methodologies – SDM, Prince, PMP and Agile
•  A strong focus on delivery.

In addition, my focus has been managing multiple projects and staff (Analysts, Architects, Developers & Testers) , to ensure that the Business Sponsor / Client receives optimum value from the effort required. Also ensuring that all concerned are fully engaged, and that all distractions and impediments are removed. I make sure that flexibility is built into the process, thus allowing for the capacity to respond quickly and effectively to change - through short iterative cycles and direct communication.

Agile - my view of Development and Project Management.

This site contains articles relating to Project Management, Agile and Scrum. Some copied from The World Wide Web, others from my experience.

Trademarks
Product names mentioned in this document may be trademarks or registered trademarks of their respective companies and are hereby acknowledged.

Everything about "my_agile"  is linked directly or indirectly to this document.; including the , a   (ane from t examplhe Reference Material folder) , Templates and Reference Material.

I manage my projects in Windows folders. this circumvents companies "Web "security setups. I also find that, currently, Windows folders are generally more acceptable. Hence most of the documents here- in are in MS formats.

As I find new and better references / templates I update them. If a reference proves popular I convert it and move it to templates.

Introduction

I  start with a "Master Index", (MS Doc). One folder for each project.  Within each project folder there are sections for easy reference (A - ZZ)
Z containing  Templates
ZZ containing Reference  Material
ZZZ containing specific Sprint, Burndown and Story materials

Note: Z,ZZ & ZZZ are removed at project close. Any Project specific Data will have been filed in " I "- Project Reference Material.

Note: The Project "owning"the Master Index is one of many projects stored  under the Project Management (PMO) Directory umbrella. An example of how that might look in HTML form is HERE!.

The second step is the Business case. And / or the Business Requirement, followed by the establishment of "sliders" and the format of the status reporting.  I combine both.

The third step is the establishment of the players, boundaries, in scope, out of scope etc.  Dataflow diagrams are the perfect tool for this purpose. As a minimum Diagram Zero, at this point.

Now aquire staff; Business Analyst, Systems Analyst and Architect (to begin with). At this point, depending on the size of your organisation, you will follow the leads described by your PMO. This will ensure continuity and supportability. Just please ensure that Operations are involved. It is they that will support and upgrade the operating systems after "Go Live".

MY ARTIFACTS

Dataflow diagrams

Dataflow diagrams (gane sarson), I find are the key to ensuring that the Project understands the Business Case and the Business Requirement. Also, on a lower level, that each story has been broken down to a deliverable junk of work. See Dataflow Diagram.pdf.

  Diagram Zero of my Agile Project Management artifacts etc.

as you can see, this site is under construction
And I am following the story estimating technique  :-)

MY SAMPLE DOCUMENTS

Sample templates include;

Critical for AGILE is the status reporting of activity . I refer to Story Cards, Backlogs, Quality, Sprints, Fault Reports, Burndown Charts, Velocity etc.

Sample Stories / Burndown / Sprint TemplateS;

Sample reference materials include;