Project Implementation I NISSMAT #projectimplementation #projectmanagement #NISSMAT #implementation

What this session covered

This session, recorded under the NISSMAT Forum, took the form of a host in conversation with a single guest: a United States-based operations executive with long experience of programme and project delivery. The speaker framed project management as a discipline that applies well beyond the workplace, and set out the anchors she relies on in any programme: recognising that every project is unique, with a defined start and end in both time and scope; establishing common goals and adjusting them as risk is evaluated; placing tollgates at essential points of the journey; managing resources, including time and collaboration; and, above all, agreeing defined and aligned success measures with stakeholders at the outset.

Much of the discussion contrasted agile and waterfall approaches. The speaker argued that agile working is not confined to IT: it is iterative and fluid, relies on frequent communication within self-organising teams, delivers a minimum viable product early so that users can respond to something tangible, and keeps documentation lighter and continuous rather than front-loaded. On team formation, she placed people skills, communication, organisation and commitment ahead of formal certifications, and advocated assembling different strengths in different people. She described matrix, dedicated, hybrid and agile team structures, noting that in her experience a matrix structure tends to sit well with agile methods, sometimes after a dedicated structure in the planning stage. Practices she emphasised included writing an opportunity statement from the customer's perspective with a cross-functional team, disciplined root-cause questioning, and proactive risk governance from the first day of a project rather than once difficulties surface.

The conversation then turned to pitfalls and measurement. The speaker identified underestimating the human side of a project, failing to establish a consistent communication rhythm, becoming too committed to an initial plan, scope creep, poor pacing and sequencing of work, and weak stakeholder engagement as recurring failure points. Success, she argued, should be judged through the lens of internal and external customers, through financial criteria, and through the engagement of the people who inherit the end state, with decisions driven by data rather than anecdote and results visualised for stakeholders throughout the life cycle. She closed with reflections on fostering continuous improvement — encouraging ideation where the work actually happens, permitting fast failure within guard rails, and attending to both large and incremental innovation — and on international delivery, where cross-cultural competence, careful expectation-setting across global teams and the ability to influence without formal authority were presented as the decisive skills.

Key points raised

• The session was a one-to-one interview with a US-based operations executive, not a panel discussion.
• The speaker anchored project delivery in agreed goals, tollgates, risk evaluation and success measures defined with stakeholders at the outset.
• Agile methods were presented as applicable to all projects, not only IT, with iteration, early minimum-viable delivery and frequent communication as the core distinctions from waterfall.
• People skills and domain knowledge were placed ahead of formal certifications when selecting project team members.
• Recurring pitfalls named included neglecting the human element, over-commitment to the original plan, scope creep and poor pacing and sequencing.
• For international programmes, the speaker highlighted cross-cultural competence, expectation-setting across global teams and influencing without formal authority.