Feb 27, 2016

Lead the online application

After leading complex online systems for few years along with time to say goodbye its also time to share experiences. Leading an organization's online system can be colossal especially is its e-commerce, online banking, social media, etc. sites. Though separation of concerns are handled via departments in structured organization - UI/UX, online, mobile, and backend teams; but for lead to be more productive & effective certain knowledge areas are must today.

Starting with Agile, lead is a developer. He or she is developing along with taking slightly more responsibility that is of mentoring and guiding other developers. Lead should be aware of Agile, create tasks, work on tasks, has complete picture of application, open to help, and bound to technology. Lead develops code and runs code. Lead also gets involved in governance and documentation. But lead doesn't take all responsibilities of everyone. He or she should not be owner of other's stuff and he or she should not be blamed for success or failure. IT industry needs self motivated developers who can not only build the show but also run the show.
Agile UX unifies developers and designers in Agile process.

Use Case documents, Requirement documents, Business Case, and Project plan are too boring. I take responsibility of rough estimates and rough budget. Interesting things starts thereafter.

Foremost is understanding Information Architecture - How information is categorized, How information is represented, how user moves through information, and how user looks for information. It takes huge effort to understand it and build the Information Ecology - apprehension of Context (business, funding, policies, culture, technology, resources, and constraints), Content (documents, volume, governance, contents), and Users (audience, experience, needs, behavior).
User Experience designers take Information Architecture to next level. Structure is important to relate scale and Sitemap allow us to visualize and relate the number and organization of website pages.

It starts with Site map - A website structure that allows us visualize and relate the website pages.
Though in Agile its all iterative but still rough sitemap should be drawn in start.
Next comes UX designs. Its said
“The UX designer must be at least one step ahead of the sprint. In other words, do research and design work outside of the current sprint. I have to keep laying the tracks for the team.”
 - Derek, Lead Researcher & UX Designer.

Next is UI. Get familiar with UI patterns.

No question we are not developing RWD; therefore UI should be shared for any page for all devices - portal, mobile, and tablet; so that development can start for that page. At the same time we architect the services, contracts, database tables, etc. Undoubtedly microservices, RESTful services, automated build jobs, and on and on.

Contents of WebSite & layout should rank Site high in Google search and SEO is solution. Understanding of Internet is must for a lead. How Internet works - IPv6, IP, VIP, DNS, Load balancer, Web Server, static content, etc. 

No comments

Post a Comment


© Shift, ShEkUP, Shape, and Surprise | All rights reserved.
Blogger Template Crafted by pipdig