When you try to transmit ideas you can repeat and repeat the ideas you want to put in other mind.
- First, tell what you are going to tell,then,
- tell it,Finally,
- tell what you have told.
The important thing is that it sounds convincing and not like a broken record,
I have sent to a service manager an e-mail with some key points we have to take care for 2011 during the service execution and that are changes to 2010.
As answer, I have received:
From: Service Manager
Thanks for the update ! This information is useful to me too.
Maybe we forward this information to team too?
To: Service Manager
You are the service manager, you have your style managing your team, apply your style,
Sometimes I am rude, but if I start answering easy questions, I will finish managing the team.
There are some conditions we have to create if you want to have a group of people as a team:
- Person competence, you need people with enough competences, some of them complementary.
- Clear & defined functions, for all team guys and clear channels of communication (inbound/outbound).
- Authority, to decide on some aspects, features, behaviours… that provide a piece of freedom that enable them to act in their style.
- Resources, to be able to perform their functions.
- Protection, we have to protect our teams: their authority, their decisions, their delivery conditions cannot be interrupted,
- Control, there should be a way to check that performance of the team is right and that they are working through their goals.
There are more conditions, these are just some of the basic ones.
In your work environment you have 2 things you take care:
- The goals related to the work you do,
- and the relationships you establish with people.
These 2 aspects walk in different directions and sometimes is complex to reach a good balance.
If your behaviour is so aggressive, you will walk through your goals but late or soon you will miss the relationships.
In case you you would be so submissive you will have a lot friends in the office, but you will not reach any goal.
In the middle: assertiveness, something we have to implement everyday.
Someone missed the existence of this balance some weeks ago and I have lost what I thought it was a good friend.
I’m very sad about this reason.
Sometimes you find involved in situations where solutions are not reach easily. Why? Sometimes is because we confuse problems with conflicts.
- Problem: it’s something logic, you can apply an solution for it.
- Conflict: it’s something emotional, there is some type of personal interference that usually does not allow to find a solution.
Take care to detect them and try to avoid conflicts
2 months ago I did a project definition trying to improve the way I do it. I focused on:
- Doing a well defined WBS,
- Dividing the “Build” phase in different waves,
- Defining clear milestones at the end of each WBS package,
- Test activities on all packages,
- Include client activities and participation in each WBS package.
Once defined it, the rest of the activities were very easy:
- Detail client activities and participation,
- trace testing plan
Invest time for doing a good WBS is a we invested time.
This project, once approved was assigned to a project manager that reviewed all the documentation and was happy to see that all project management best practices were on those documents.
We also have detected things to be improved, so I’m happy about it too.
List to for reading before define requirements:
Unambiguous: Precise and clear with only one interpretation. Consensus agreement.
Complete: Every known aspect is described.
Consistent: No contradictions, uniform terminology used.
Measurable: In terms of time and cost, can it be estimated? Can it be verified against the implemented solution?
Testable: Requirements should be quantifiable.
Traceable: Must be able to track from project inception to delivery.
Design-free: “What” not “How.”
- Understandable: Able to be understood by non-technical customers, system users and developers.
- time for numbers,
- time for forecasts,
- time for agrements,
- time for details,
- time for defining new scope,
- time for removing old services,
- time for welcoming new services,
- time for closing gaps,
- time for learning,
Out of scope:
- time for blog
- and other hobbies
almost finished!!! yuhh juuuu
Learning the manufacturing language,
SKU is a unique identifier for each distinct product and service that can be purchased. SKU use is rooted in data management, enabling the company to systematically track its inventory or product availability, such as in warehouses and retail outlets. They are often assigned and serialized at the merchant level. Each SKU is attached to an item, variant, product line, bundle, service, fee, or attachment. SKUs are often used to refer to different versions of the same product.