Andre de Godoy Nunes

We have a new scenario into all organizations where traditional approaches to Portfolio and Project management are simply not delivering the results that today's businesses require. In fact, poor portfolio and project management performance could be costing your business up to 46% of the planned ROI from your project investment. So what you don't know can affect you negatively. For example:  Are you aware of annual planning's shortcoming? or do you know why project success rates are typically poor? or even what about the impact of low budget utilization? PMO teams are feeling the pressure from high management and executives to find better ways to clearly demonstrate their value to the business. So which would be your next move? Some suggestions would be adopting a more strategic PMO mindset, identify and replace inadequate tools, integrate investment planning and controls to drive financial maturity, move from annual planning to dynamic reallocation, create a culture...

Dear readers, first I would like to apologize because my English writing is not really good. I am not an English native, however I am trying my best to improve my skills. I hope you understand that. Before starting an agile project it is usually necessary to perform some dynamics with the Scrum Team to facilitate the composition of product backlog. These dynamics are called INCEPTION meetings. In meetings like that is where the product scope statement is developed. Techniques such as Product Vision, Impact Mapping and Stories Mapping (Story Mapping) are initially applied to delimit the boundaries of the scope to the product and direct the focus of the work, which later user stories will be used to start the composition of product backlog. Creating a Clear Product Vision Product vision is quite important to the success of the product. It seems a simple statement, right? But think about how much impact it can really have in the project. A product vision gives us ...

Dear readers, first I would like to apologize because my English writing is not really good. I am not an English native, however I am trying my best to improve my skills. I hope you understand that. Regarding agile practice, it is common this question:  Why use a technique such as User Story? Using this technique assists in identifying a logical business requirement, allows breaking requirements in small pieces of requirements and also allows structuring these many requirements on a type of tree that will be a baseline for documentation. USER STORY  is a technique for identifying and organizing business requirements using stories told by users as they describe themselves their needs. User Stories are artifacts developed and managed by agile practices. Using User Stories not necessarily there is a need of interaction between actors and a system or software tool, once this interaction can put focus on the activities of the process. 3C Concept (Card, Conversation and C...

Dear readers, first I would like to apologize because my English writing is not really good. I am not an English native, however I am trying my best to improve my skills. I hope you understand that. I would like to suggest three steps to anyone who wants to get into the agile life.  These three steps were quite important to my career and maybe would be a good start to you too. 1) Read the Agile Manisfest at http://agilemanifesto.org/ and try to understand its philosophy in deep. It is a good idea reading it also in your own language in case of you not being a native English person like me. 2) Read the Scrum Guide in English and also in your own language and try to understand its philosophy, practices and structure. You may download it in pdf format at http://www.scrumguides.org/   Scrum is most about project management using agile practices, but it is quite good to understand the dynamic of being agile and its value. Later you may go to other area of study su...