Skip to main content

Software Process and Covid - 19

During this pandemic, WHO and other government bodies have been giving guidelines and instructions to ensure our safety. Most people read thru these guidelines, some understand, few follow and less adhere. Even with the lesser, the effectiveness is questionable because, the guideline is just followed. With 14 years of journey with process, can't help but compare the current scenario with "Process compliance" in Software Quality


Process Compliance Mishaps
Process is
  1. Taken in by the team irrespective of the fitment
  2. Followed strictly (only) for sample releases to showcase it to the certification auditors
  3. Felt as an unnecessary, forced add-on to the delivery cycle
  4. An effort drainer for the software engineers
  5. Used as a weapon by senior management to punish the mistakes
Do not follow Process
  • Focus on the Process intention than the guideline - Like, review is to identify the defects early, do not focus on meeting the org target
  • Process should be seamlessly integrated to delivery. - > Use tools like Jira,TFS effectively. This blog site is gonna cover more aspects of JIRA way forward
  • Process is a tool for better delivery not to assess people
  • Ground level team should be aware of the process intention, which will also bring in more contribution for process improvement
On Summary " Do not follow Process", Pursue the process objective .....
Labels:

Comments

Post a Comment

Popular posts from this blog

Schemes : Assembling the building blocks of Jira

In a classic Jira project there are building blocks which is required to be created and assembled to onboard a project .Those building blocks like, project, issue types, workflow, screens, permissions and notifications are independent entities. They do not converse with each other. E.g.,  Team A has created a Jira project as "Legos" and two issue types are decided "Story and bug" to be tracked. The team has also gone ahead and created two workflows for Story and bug.  Now as these building blocks are created, they are independent, The issue types chosen will not reflect under the project or the issue types will not traverse as per the workflow, because they are not linked to one another "Schemes" are used to assemble these building blocks.  Each of the blocks here will have the separate schemes created and integrated. This blog shares details on the concept, creation and linking of each schemes to the project Issue type schemes Issue types are the list of
1 comment
Read more

JIRA Screens - Make it better and effective with the What, When and How technique

JIRA - Originally a bug and Issue tracker has evolved into a powerful work management tool.  JIRA is built on a concept that allows users to design their own delivery solution model . Various parameters of JIRA, like workflows, screens, notifications, permissions and so on can be customized to our model Of all other parameters, "Screens" are visible and interactive to the end user. Designing of screens should be more thoughtful to ensure better experience . Sharing you, the WHAT, WHEN and HOW technique for JIRA Screen design WHAT data to collect While you design a screen,  the first step is to understand and consolidate all the information required for the issue type  For e.g. Story Vs Defect Story = Epic details, Story points, effort, Dependencies, Feature,etc., .  Defect = Severity, priority, Affect version, fix version, Impact details,etc., Consider gathering Information from various sources, to ensure maximum coverage. Following are few of the sources which you can refer
8 comments
Read more

Building blocks of JIRA

Jira project on-boarding, in a classic project of Jira there are key building blocks which needs to be modeled and assembled, to ensure successful on- boarding.  Not only for the Jira admin's,it is also important for the end user and requirement givers, to understand the building blocks and their interaction. This add-on will bring in a different perspective on what to expect from Jira. Pictorial representation of how the building blocks are layered is shared below 1. Projects A project in Jira is the level at which you want to track your delivery / execution. A Jira project need not necessarily be the same as your software Project.  Example: You have a project signed for Customer A and you have formed 5 teams: Software, Hardware , Ux, Information development & security team. So now, you can have your Jira project tracked at the customer level or at the team level You can also have a totally independent item, which is not part of your project life cycle, like Organization custo
3 comments
Read more