I can’t wait to attend the 3 days Scrum Master Certification by ISS. Ever since I was first introduced to SCRUM, I’ve been trying to practice it.
However, I din’t really get the chance to practice it fully as the companies I’ve worked in are very much following the old “Waterfall Model”. And I also believe they are not ready to work with SCRUM yet.
But I have been slowly applying SCRUM principles and techniques into the process, skipping the terminologies and all, hoping to get them comfortable and one day they will realised “Oh, we’re actually using SCRUM.” –if they actually know what it is.
With this certification, I hope to encourage people the best practices of SCRUM and to particpate in a SCRUM team that appreciates it.
You will always be describing a process. Determine the process that is to be automated, and describe it.
You must understand something at one level before you can truly understand it at a lower level. Start your analysis by describing the overall process at a high level of abstraction to form the framework of the rest of your analysis.
You must describe “What” not “How”. The business process should be described independent of how a system would help a user to complete the process.
Follow the “80/20 Rule”. The “80” = the main process flow, when everything goes smoothly. The “20” = the variations from the main flow.
Describe each step and sub-step in a process as “Somebody does something with some information”. This syntax will help describe the process in a way that is understandable by all, and will lead to the simple identification of the true business requirements.
“Common sense is the most widely shared commodity in the world, for every man is convinced that he is well supplied with it.” ― René Descartes
Isn’t most things in life strikes us as common sense? Or at least, that is what I thought so, same for many others. But common sense is not so common.
“Common sense is seeing things as they are; and doing things as they ought to be.” ― Harriet Beecher Stowe
Common sense “should” be the root of all analysis. However, common sense is highly subjective and requires definition. Many people see things differently, think differently and thus doing things differently with reasons behind it. And I do think it’s rude when one says “Use your common sense”.
We all knew about the PSD-to-HTML workflow but with the introduction of Responsive Web Design (RWD), the workflow has to change.
Given the complexity of RWD, initial planning like content strategy, IA, sketching, prototyping without considering layout changes and alternate viewports may cause opportunities for optimization and innovation to be overlooked.
Also, we can’t be producing PSD for each page and/or view variations, it’s crazy.
Improve on how we craft webpages and the deliverables produced with Dave Rupert’s Responsive Deliverables. This article tells us to break complex page layouts into reusable solutions in terms of modules.
Learning and self-improvement has always been a part of me. And one needs to proactively embrace new approaches than try to shoehorn an old one.
If you want to know more about designing in browser, you can read the Pros & Cons.↩
Increasingly, companies have finally adopted responsive website design. To me, this is not a trend but a necessity; given how smartphones and tablets affects one’s life.
In the past, companies created multiple versions of their websites for mobile users. This is not practical hence responsive design approach saves the day. Although responsive website design has been in the scene for many years, I realised that there are some people who are still confuse between mobile sites and responsive sites.