My domain coverage of Project/Program Management
Lets look at time schedule of typical Agile Project Manager.
Agile project management is new stream Added in project management certification where concepts of Six sigma , Statistical process control were added into project management.
This is Newest Addition into project management. These topics are not yet included in popular project management certification altogether a new certification was made for it.
Here is link for certification:
Every new requirement are written in form called user stories. The User
Day Work starts as move from home
Wake up 06 am go for 1 hour gym 06-07;30.
07:30- 8:00 daily routine, etc luck enugh time take break fast.
07:50 reach bus stop to catch bus.
07:50 – 09:00 on road to Company.
9 am-10am look at a parameters to check status of project like burn down chart to see how many user stories are covered upto now. prepare new set of activity List not next drop Testing environment.
10-11.30 Scrum Meeting: To check Who is doing what and What is status of Activity Assigned. Also Take Activity list and Check Assignment and discuss possible issue around then from each a every team member. A team of 40 people each taking 2 minutes(highly unlikely people do take more time) adds to 80 minutes.
11:30 – 11-45 take all this feedback make Minutes of Meeting MOM.
11:45-12:00 make assignment of every activity taken up by each resource and recheck plan to see whether its on target to testing cycle next drop.
12:00-12:15 adjustment in plan. update burn down chart send to stake holders with project status.
12:15 Take look at technical issue hitting limits requiring attention suppose 10% of team faces means 4 people each requiring 15 minutes to understand issue and then another 30 minutes to implement solution.But in that 30 you can use 15 minutes to move to another member just paralleling h=job save 15 min per interaction.
12:00 -12:30 Team 1 issue.
12:30-1:00 Team 2
01:00 -01:30 Team 3 issue.
01:30-02:00 Team 4 issue.
By 2 free to take Brunch
02:00 – 02:30 Lunch+ going and coming time.
02:30- 03:00 meeting With Requirement gathering team for new user Stories for next cycle of deliverable. Understanding requirements and putting them into actual activity considering integration with delivered Earlier.
03:00-3:15 put all user stories in official format.
3:15 – 4:15 Code walk through check issue, Compare best practises incorporated, Standards, Regulations etc Each day of different team. Although time would less optimize.
04:15- 05:00 Look into specific issue not handled today, defect pending long, make communication mails between stake holders and reply to all status, calculate project status ratios and levelling, resourcing issue etc.
05:00-06:00 Defect Call between Testing Team and Development team. update defect list Those accepted as defect added to list to be taken up by developer and Those defects found by testing team turned down by development team as not fitting user stories description so moderate the discussion getting into each defect technicality and correlating with requirements.
06:00-06:15 Take daily status from each team member of work completed today and put that against project plan send to stake holders.
06:15- 06:45- update defect sheet, Look at technology issue which faced today help team member in possible resolution.
06:45-07:45 If 10% issue of the day would still be remain and project artefacts would require updation. it may take up 1 hour depends on complexity of project.
07:45-08:00 Dinner time.
08:00-09:00 Research time on possible better ways or project is taking any new technology implement and study, visualize its impact on future deliverables. Like one Example: There Was a issue on Report using Oracle BI solution when start fetching data from various data marts and databases taking more time and not having some feature.
So Question is Can we replace BI with portal based UI creation technology like Oracle APEX. Did you hear about it ? it was released in year 2009 and was new technology with hardly 4 resources in Whole company of 30,000 developers. So can we put geographical reporting using APEX rather than OBIEE. Mind you its not the APEX code used in saleforce.com’s Force.com platform to create CRM on cloud. Can u up scale in 1 hour about this issue. No first day of the 8-9 time installation, second day 8-9 get basics right at end of week you have replicated the environment. Then you may need time over week ends to experiment.
9:00 -9:30 leave from office wait for Bus.
9:30-10:30 home drop. walk to reach room by 11.
At 11 just drop and read watch sleep.No time. I had never touched facebook when I was working my account came to existent when I left job.
Now there are other activity for which yo might have to take time out for company like creating organisation assets in form of automated solutions, or project status reporting framework, business Case development, team building , taking interviews, over seeing the drop to testing and production, interaction with diverse team member sparse across. build up domain skills of like telecom OSS, BSS or Clinical research etc.
Or taking up groups of competency and giving training to user and developers etc.
When these are adjusted time may swell up more in office. So u may not see sun rise whole day started before sunsrise and Ended in midnight. After few years it will become norm although companies write work life balance but they could never provide due to competitive bidding process takes up less and less for more and more work.
One more issue is attrition: now if attrition is high due to organisational issues then it does add up to work of senior staff to upskill new resource and adjust timings. These are thin lines over which Everything rest each day you will find your self motivated to do more in less time to save time automatically but new things will keep comming.
Last 8 months:
University Exam :
term end 10 cleared 10
Mid term : 10 cleared 10.
Other University Exam: 12X15= 180 Exams
Cleared = 120/180.
Other University course cleared: 12.
Exam per month: (180+20)= 200/8= 25 Exams per month.cleared 15 per mnth
25/4= 6.25 Exam per week: cleared 4 per week.
+ 180 plus courses video lecture (120 exam cleared).
hours spent on Online lecture: (6.25 X 3 hrs)=20 hours per week.
hours spent on live lecture: 10/20 hrs per week.
Time spent on exam: online per week: 4 X 2= 8 hrs.
Time spent offline University Exam : 12 X 3= 36 hours /8 month = 4.5 hrs/mnth
= 1 hr per wk
Total time spent on Education
Online Lecture+ Exam: 20+8= 28 hrs / week
Offline Lecture+ Exam: 15+1= 16 hrs /week
Revision 20% time = 9 hrs / week
Total : 53 hrs/week.
238 hrs/ month
1908 hrs/ 8 month.
Skill data point generated: 180 X 20= 3,600 data points.
Elaborate more in next article how to Analyze more deeply this about categorization using Market basket and profiling:
Extras: personal Schedule this year:
95 hrs/week : or 95/7 =13 hrs per day (including weekend)
95/5 =19 hrs per day (excluding Weekend)
Enterprises can be large and complex, the models associated with the discipline also tend to be large and complex.Enterprise Architecture framework help reduce this complexity by offering:
A list of ALL ENTERPRISE FRAMEWORKS…
– Business Frameworks (e.g. BMM, Six Markets, Porters 5 Forces, McKinsey 7S, etc)
– Architecture Frameworks (e.g. PEAF, MODAF, TOGAF, TEAF, IAF, Zackman etc)
– Programming Frameworks (e.g. .NET, J2EE, etc)
– Project Management Frameworks (e.g. PRINCE2, MSP, etc)
– Service Management Frameworks (e.g. ITIL, etc)
– Industry Operations Frameworks (e.g. eTOM, Pragmatic Marketing, etc)
– Any other type of framework in any other domain so long as it is related to an ENTERPRISE.
There is endless list of model basically modeled around either Zackman or TOGAF.
Like this one for security. Building Security In Maturity Model. The BSIMM is a study of real-world software security initiatives organized so that you can determine where you stand with your software security initiative and how to evolve your efforts over time.
then like sharewood which like modeled on zackman
As Agile project management incorporates principles of Lean techniques , kaban and six sigma into software development life cycle. Lean comes into picture as instead of huge inventory of requirements getting stacked in Product/Project Backlog an inventory is kept as small or as lean as possible. Security feature or requirements are more costly if not caught early in life cycle or product development life cycle. Paper discusses lean management of security requirements. Also application of Security Testing Methodology , application of Security patterns anti-patterns to increase Reuse and reduce time and reduce cost.
click to download document in word format:
Information security has become most critical aspect of any firm today. From protecting intellectual property for any company where patents company hold is substantial part for their business. Actually company shell out huge money for Acquisition and merger just to get patents like google acquired motorola mobility for getting patents related to hand held device, Microsoft acquired skype fot entering into telecom protocol and SIP phone based markets.. So now it more important for them t protect using security measures. Same way sites like Amazon which is book seller, best buy for retail same way there are companies which are emerging on web which are taking away the traditional way of doing business essentially everything is coming onto web. So we have Wen 2.0 then Web 3.0 to cloud computing where platform as service PAAS , infrastructure as service IAAS, Software as Service everything is exposed on web. its becoming more critical for them to manage security.
Biggest problem in Security is how to define security which i covered some part in my last article but there bigger concern how to manage security projects. Because traditional way of SDLC or software processes does not apply to security due to huge dimensions it can touch like a threat may come from software defined by OWASP , or Web interface still OWASP, or may come from OS (virus, malware, torjan etc…) or may be at assembly level, or may come from hardware recently DSS algorithm failing for ATM cards (PCI DSS standards) or it may come from operational lapses not captured in audit or it may come from transmissions of signals making data exposed to and machine catching signal or sensor network, or network layer Router switches or it may be in mathematics of encryption and decryption which is brooken. Domain is so vast that pointing 1 fault is sometimes mistake. Problem is: defining requirement has bigger problem but more bigger problems are which managing such projects. So what it takes to manage such project? traditional view of PDCA Plan – do – check – Act does not take emergency situations and penetration testing when its done on software to website or and protocol or technology..PDCA is valid when u are creating a project of pen testing but for maintaining security is continuous task testing methodology like OSSTM provides help only in Application security project not for network security or OS security or any there part security.. so security is continuous project..it requires exhaustive preparation.