#DevSecOps for kids

Hey there, kids! Have you ever heard of something called “DevSecOps”? It might sound like a strange and complicated word, but don’t worry, we’re here to explain it in a way you can understand.

Imagine you have a special secret box where you keep all your toys, and you want to make sure it stays safe. DevSecOps is like taking care of that secret box, but for computer programs and apps.

Let’s break it down into three parts: “Dev,” “Sec,” and “Ops.”

1. Dev (Development):
When people create computer programs and apps, they are like toy builders. They design, create, and build these digital toys. In the world of DevSecOps, this is where everything starts.

2. Sec (Security):
Just like you want to keep your toys safe in your secret box, computer programs need to be safe too. This part of DevSecOps is all about making sure the digital toys are protected from bad things, like hackers. Think of it as putting locks on your secret box or having guards to watch over your toys.

3. Ops (Operations):
Now, after building and securing the digital toys, we need to make sure they work smoothly. This is like making sure your toys are ready to play with whenever you want. It’s all about taking care of your toys and keeping them in good shape.

DevSecOps is like a team of grown-ups working together to create, secure, and take care of these digital toys. They build them, make sure they’re safe, and keep them running well. This way, people can use these digital toys without worrying about any problems.

So, in simple words, DevSecOps is about creating, protecting, and taking care of computer programs and apps, just like you do with your toys. It’s a way to make sure everything works well and stays safe in the digital world.

Now you know what DevSecOps is, and you can think of it as a big group of helpers making sure your digital toys are awesome, secure, and ready to play with!



Lost opportunity cost…..#pmot…#in


In the last post we discussed risk aversion. One of the pitfalls of being too risk averse is lost opportunity cost.

In New Product Development Project Managers constantly balance time to market with product quality, resource management, project costs & a host of other competing factors.

In an effort to develop the perfect product with maximum process capability and meeting 100% customer satisfaction the real cost of lost opportunity is often missed.

Consider a product which on release will generate, on average,  $100,000 profit a month for 12 months. If the product release is delayed by 1 month the lost opportunity cost can be estimated as $100,000. What should be  emphasised is that this amount will NEVER be recovered. If the product lifecycle is estimated as being 12 months depending on the competition then releasing the product 1 month late reduces the lifecycle to 11 months.

If that lost $100,000 was invested at a compound rate of 5% per year over ten years it would be worth $163,000 !

So here are some tips to minimize lost opportunity cost:-

1) Invest in the project at the front end, providing ample resource and support.

2) Fix the product spec before the end of the design phase.

3) 100% perfection is great but 95% is normally good enough for most customers.

4) Make it easy for engineers by setting SMART (Specific, Measurable, Aggressive, Realistic, Timely) targets.

5) Publicise Project Milestone targets.

6) Communicate Lost Opportunity Costs.



Follow projectsguru on Twitter

View Chris Robinson's profile on LinkedIn

; Keep up to date by becoming a  facebook

project managers and business consultants

Nokia upwardly mobile….#pmot…#in

  • “We poured gasoline on our own burning platform. I believe we have lacked accountability and leadership to align and direct the company through these disruptive times. We had a series of misses. We haven’t been delivering innovation fast enough. We’re not collaborating internally. Nokia, our platform is burning.” – Stephen Elop, CEO Nokia.

nokiaThe recent internal memo “leaked” from Nokia & published on technology website Endgadget.com demonstrates the need for any corporation, but particularly those in the Technology arena, to have a continuous stream of new product developments flowing to the market. This is the direct result of a new product routemap which clearly identifies Customer needs, market trends and technology requirements.

New Product Development should not be a haphazard process but one which is planned years in advance. It should also be adaptable to allow flexibility in the case of new technological or market developments.

Not so long ago Nokia held pole position in the mobile phone market with huge market share. Now they are languishing behind Apple & others in the
Smartphone arena and are struggling to compete with Chinese manufacturers at the bottom end of the market.

However, all is not doom and gloom. The new CEO Stephen Elop obviously
recognises the problems and is keen to address them. This is the key important step in any recovery. Rather than just bury his head in the sand he is tackling the issues head on which is good news for Nokia empoyees and shareholders.

If you need help with your product development process get in touch NOW!



Follow projectsguru on Twitter

View Chris Robinson's profile on LinkedIn

; Keep up to date by becoming a  facebook

project managers and business consultants

1o ways to invigorate teamworking #pmot #in

teamworkMost people involved in New Product Development agree that best results are obtained when people work effectively in teams so here are 10 guaranteed ways to improve teamworking:-

1) Locate the team together in the same room. – If people sit together they work together. It is essential that the primary form of communication is face to face. There should be some allowance for privacy but any cubicle walls should be below head level.

2) Locate the Project Manager in the same room – As the Project Manager there may be a tendency to remain distant or aloof from the team. This is counterproductive and wrong. The Project Manager should be located in the same room as the team. If She has her own office the door should be left open to allow ready access. If She sits with the team there should be a private office available for personal discussion.

3) Hold regular team meetings – although there may be some resistance to this (too much work etc) it is essential that the team meet at least once a week to discuss project status.

4) Issue meeting minutes – It helps communication if everyone knows exactly what is expected of them following the team meeting. The minutes also act as a good crib for next weeks meeting.

5) Promote a democratic culture – environments where people feel free to speak their minds openly and honestly lead to faster problem solving and decision making.

6) Promote team activities – 5 a side football or similar activities are great if everyone is  fit and active but be careful to choose something EVERYONE can take part in otherwise you will alienate some team members and defeat the purpose. I have always found bowling to be a great choice which just about everyone can do.

7) Eliminate the Blame Culture – resist every opportunity to blame others and take responsibility for your own decisions. Blame Cultures are endemic in some organizations and will take time to be eradicated but the changes in performance will be immeasurable.

8) Listen twice as much as you talk – we all know the old saying about empty vessels making the most noise and no where is this more true than in Project Management.  Try really listening to people and see their reaction.

9) Put the Structure in place – whether its based on PRINCE2, Project Management Institutes PMBOK or some alternative combination, Teams are more effective when they no what the rules are.

10) Keep a sense of humour – as the Project Manager nothing upsets or disorients the Team more than a panicky Manager. Keep a sense of perspective, enjoy the fun bits and lead by example.



Follow projectsguru on Twitter

View Chris Robinson's profile on LinkedIn


10 tips for faster leaner new product development #in #pmot #lean


Bringing New Products to Market faster & more efficiently is even more critical as product life-cycles shrink so here are 10 tips for faster, leaner New Product Development:-

1) Nail the spec early – the sooner the product spec is finalised the smoother & faster the development will be. Less time & effort will be wasted debating the minutiae if the spec is closed early.

2) 5s the area – Apply the Lean principles of 5s (see earlier post) to remove unnecessary distraction and promote “clear thoughts”

3) Promote re-use in Design – to reduce design effort and make best use of proven and qualified technology.

4) Parallel Planning & Design – Design is normally the longest phase in New Product Development so why wait until the end of Planning to start Design. Start Design in parallel and adapt the plan when more is known about the length of the design phase.

5) Arrange Regular Reviews – during the Design phase and break the task into smaller “chunks”. Design is one of those tasks which has a tendency to expand to fill the time allowed for it.

6) Structure the Innovation process – ensure that Innovation board reviews are scheduled well in advance and board members have suitably qualified deputies so that stage gate reviews suffer no delays due to the absence of key personnel. The Innovation process should become Institutionalized.

7) Dedicated multifunctional Teams – are more effective than matrix teams  If resource allows.

8) Design for Manufacture – manufacturing & production engineers need to be involved in the product development process to ensure a smooth transition from development to manufacture.

9) Minimize interruptions & noise – in the product development area.

10) Promote a democratic involving Management style – to increase free discussion and mutual respect.



Follow projectsguru on Twitter

View Chris Robinson's profile on LinkedIn


“Give me a faster horse”

modelTHenry Ford once commented that if he’d asked his customers what they wanted they would have replied “Give me a faster horse”.

Sometimes in New Product Development we have to take a Quantum leap in imagination so that we can develop products which no one else has imagined.

“Brainstorming” is one techniques to help that process:-

1) Form a team of maximum 10 people drawn from all levels of the organization.

2) The “Chairperson” should be mid level with no obvious authority.

3) Provide some drinks and snacks to create a relaxed atmosphere.

4) Go round the table asking each one in turn what products they think the Company should be developing.

5) Don’t reject anything at this stage.

6) Don’t criticize anyone else’s contribution.

7) Get someone to list all the contributions on a whiteboard.

8 ) When all contributions are exhausted arrange them into different categories.

9) Vote on the top 5.

In the next post we will explore how to take these ideas forward.


Follow projectsguru on Twitter

“If you don’t know where your going…

product roadmap

product roadmap

any road will take you there.” – Lewis Carroll

To increase the success ratio in New Product Development it is essential that your company has its own New Product Development Roadmap.

This Roadmap highlights the Products your organization intends to develop in the coming years.  These product developments should be based on sound market intelligence, garnered from current customers and taking into account market developments and competitor analysis.

The New Product Roadmap doesn’t just identify market opportunities. It also takes into account the Technologies, Resources, Finances, Production Capacity etc etc so that the whole Organization knows exactly what needs to be put in place so that that the New Products are launched successfully.

The New Product Roadmap needs to be approved at the very top of the Organization. It is a “living document” which should be reviewed on a regular basis and updated as required.

The adoption of a New Product Roadmap clarifies the direction the organization is headed in and ensures that everyone is “singing from the same Hymn sheet”

“If you don’t know where you’re headed any road will take you there”



Follow projectsguru on Twitter