Built-in Quality@Work

A VAS guy should be proud of his work !

This is a quick minute about what I think about the Scrum – what it echoes with me when I hear someone talk about it. This one is about  – yes you guessed it – quality we build into our beloved VAS.

I realized that when your team developed into the we-are-together-in-this mindset, the next step was the continuous improvement to what were doing each day. It essentially became the idea that tied to everything. After every project, we set down and thought about what was good and every principle that got approved went  into action, becoming part the way we tried to put quality into our work.

I believe that we had really a value-centered mindset because were proud product people who believed that everything we did had to be bringing value to our customer.I can’t really think of a better approach from a product team really. And to think that we were there and doing that a decade ago…

Posted in agile, Product Life Cycle, project management | Leave a comment

Sometimes…

All it takes a photo look back across the years…

Posted in Unsorted | Leave a comment

My Experience With Scrum@Work

Scrum made us live better in a place where constant change was the only constant.

I worked for a very very large company in the ICT domain, and while it was not considered to be an AGILE shop, as a VAS team we operated solely in that framework for 7 years.

First of all – let me say that it was a successful marriage. Scrum is good for developing products for a Telco, where anything changes anytime…

Secondly it was successful since it worked with people for the people. If your team is of the right mindset you lose all those negative things that make a work place an unhappy one – stress is there but managed. The process made us human again, giving us chance to fix things that are breakable, developing skills that matter for people and foremost –  appreciated, at the end of each sprint. Team felt the responsibility for the team as a one!

The system worked because it gave everyone  what they needed, Autonomy for product developers, mastery over the product’s road map for PO and etc. Also, Scrum developed excellent team working skills since it forced the team to fail at early phases – and that is good as we know and yet enabled us to re-start fast or maybe – if the conditions warranted it – withdraw from project  completely, trust me we have done it more than once.

For the company it pressured the organisation to pick only one decision maker for what is to be done/not done and changed and therefore getting rid of the multi-headed project management style previously. It made us to decide with clarity and certainty what will be done in the next 2 weeks ( ie the sprint) and what comes after. This gave the organisation the ability to choose, change or even completely change the direction for the backlog. But probably the most important thing that comes to my mind is that Scrum doesn’t require and even bans planning all the details of the work upfront. It valued only productive work something we had a lot of before this became our way of life.

We also liked Scrum since it doesn’t penalize the development teams for not being clairvoyant about the remaining amount of work – we all miss a turning right ? –  similarly it also gave the business owners a second chances card for not guessing the scope of work correctly in the first time ( and we all know that they use that several times).

On the other, let me bring some memories from the “Waterfall” it replaced. For us this was a model in which each tier of the organizational hierarchy choose what they consider to be “valuable to my career part”, and passes the rest down the line. Most of the time I have seen product projects defined by executives with little idea about what they squirting from their mouth about something they have no idea about, the design being done by sales people, personal deadlines were set by middle managers who wish to go on a holiday. Most of the time some sort of basic  implementation was performed by the top-tier “brogrammers” and then the remainder such as operations and testing are handed off to the lower grade programmers. Yes it was that bad… It is a known fact that if people have a sense that all of the important decisions have been made and they are not part of the decision, they will not be motivated to do their best.

Don’t get me wrong I am not a Scrum fan boy, but it worked, it helped to save lives, and well for us the other alternative was pure pain.

 

 

 

Posted in agile, Funny, Mobile, Product Life Cycle, waterfall | Tagged , , , | Leave a comment

To get involved or not get involved…(Part2)

As an addition to the former post, just want to underline some more tips for an effective project scope management by the organization who do care about scope management.

=The companies should make sure to confirm the deliverables as frequently as possible with the customers to avoid any last minute changes ( and dramas that follow )

=They must involve the entire teams that are related to the scope in the process of scoping for the Project

=They should try to Include all the deliverables in the WBS in a very precise manner.

=They must certainly involve all the stakeholders during the requirement gathering phase. If they dont inpout now, “then” it will be too late.

Additionally the companies must be very careful about the changes that were not part of the original scope. That is really what is known as a scope creep and PM must ensure that the project scope goes through CR process.

Finally, whether one stands in early or late inclusion in the process – proper scope management is important for the company as it greatly improves the ability of the PM team to stay within budget and use time effectively.

Posted in agile, project management | Tagged , | Leave a comment

To get involved or not get involved…(Part1)

Recently I had discussion with a colleague – ” is it important or not important for functional organizations to be involved in the project from the time of the original proposal ?”

Since we couldnt find the time to finish our conversation – I decided to put my ideas here so you he can read it. Maybe I will make a series about this…

I have read that the PMI conducts a survey about project failures every year and publishes the result. This report on the state of the project management and what actually cause the projects failure is an important indicator about this issue. The result states that only roughly more than half of the projects meet the original scope! Scope creep as this called is an important reason for the failure of the projects.

Companies should be very wary about this , un-controlled or poorly managed scope issue since it can and certainly will affect their projects severely. Some of the resulting failures are missing deadline, budget overrun and even project failure. It is because of this companies need to be in the scope process from the get-go.

Early participation in the scoping process ensures that the project has a clear scope. Companies should also make sure that the project is in line with the scope and does not encourage in anyways the scope creep threat and this should only be possible with presence from the start. Additionally company should continuously check on the progress of the project with an eye on the scope.

It should be noted along with this early participation companies should als benefit from project management practises. ie it will be much easier to manage the scope of the project using effective customer client communications, staying within the limits of company’s deployed team to deliver, properly documenting important events in the development process and staying within the guidelines provided. These are all great ways to manage the scope effectively for the company but these has to be done from the day 0. This is why the company needs to be in the frame from the earliest possible time.

Posted in project management, Unsorted | Tagged , , , | Leave a comment

S@S a short video

Scrum at Scale is an extension of the core Scrum framework in a very simple way. It is designed to saturate an organization with Scrum. All teams, including Leadership, Human Resources, Legal, Consulting & Training, and product & service teams, implement the same style of Scrum while streamlining and enhancing an organization,

I have decided to upload this small video of some slides from a presantation that I gave sometime ago. Hope you enjoy it…

This slideshow requires JavaScript.

Posted in agile, Product Life Cycle, project management, S@S, SAFe, scrum, Unsorted, XPM | Leave a comment

Bir Donusum Hikayesi

Bir Turk olarak gastronomik tercihim genelde kadar her zaman et ve hamurdan yana idi. Acikcasi mideme gomdugun hayvanlar rahatlikla buyuk bir ciftligi doldurur diye dusunuyorum simdiye kadar. Tabagin kenarina ayirdigim yesillikleri saymiyorum bile.

Bir sure once gecirdigim bir rahatsizlik sonucu doktorum bana daha fiber agirlikli bir diyet onerince ne yapacagim diye dusunmus idim , inanirmisiniz Fast Food restoranlarinin onunden gecerken bile iceriye ozenerek bakardim.

Ancak onceleri biraz zorunluluktan basladigim yolculukta benimle ilgili degisen seylerden birtaneside belkide bu terchim.  Derler ya her koyu sey icinde bir de iyi bir sey vardir diye. Buda onlardan bir tanesi.

Uzun bir suredir kirmizi etten uzak duruyorum ve yediklerimi cok begeniyorum. Tamami ile hayvani urunleri birakmadim ama bir zaman icinde bu noktaya – istedigim takdirde – inaniyorum.

Bu surecte, denedigim yemek ve urun tercihlerinin hepsi cok basarili degildi dogal olarak. Neticede gida secimlerim gunumuzde biraz kisisel tercih dogrultusunda olmaya basladigi bir endustri haline gelmis durumda. Bu yuzden piyasada bir cok urun ve recipe var deneyebileceginiz, bundan sonra arada bir bu konuda rastladigim urunleri ve kendi yaptigim urunleri burada sizinle paylasmaya karar verdim. Bu tabii bir gastronomi blogu degil,  sunumdan daha cok icerik kaygisi ile yaziyor olacagim o yuzden neden bu urun , neden tabak rengi su renk degil vb. gibi kaygilariniz varsa baska bir yaziya yonelin derim.

Image | Posted on by | Leave a comment